5 ms·
Right now the only way to listen for changes on the server is through the Node.js SDK provided in the professional/enterprise editions. The open-source Node.js
by bigfish24 10y ago
Right now the only way to listen for changes on the server is through the Node.js SDK provided in the professional/enterprise editions. The open-source Node.js SDK does not support opening/writing/listening to synchronized Realms.
This is extremely helpful feedback, as we have been exploring how to expose this functionality at lower prices or in the free developer edition. One option would be to include the ability to register listeners through the dashboard similar to AWS Lambda. Would that help?
- matt2000 10y agoI think my ideal scenario would be to have a Java API similar to what android has, but running on the server with a sort of global view of the data. Then it could listen to whatever it wanted to and issue notifications, send emails, etc. That seems like it would be killer since it leaves all the error prone sync and data update code to realm, but still lets the server do whatever it needs to once it sees a change.
- bigfish24 10y agoA server-side Java SDK is on our roadmap. The current version makes use of Android functionality, like the looper, so we need to transition it. Already, the Node.js SDK has an API where you can register callbacks across Realms, giving you the global view you are talking about. You just pass it a regex pattern of the Realms you want to listen to. This functionality lives in the shared C++ codebase so once we have Java on the server, it would also have it (we also plan to migrate our .Net SDK as well for server-side use).