4 ms·
The meteor app gets packaged and deployed to a mobile device. The blog references code updates from "a" server. I'm confused- are you still running a server?
by sgslo 12y ago
The meteor app gets packaged and deployed to a mobile device. The blog references code updates from "a" server. I'm confused- are you still running a server? How does the packaged app know where to pull these updates from? Does the client share persistent data with this server?
- arbesfeld 12y agoMeteor dev here. When you bundle a Meteor app, you specify a server which will handle updates (and server logic). You can push new versions of the application to this server, and all mobile devices will automatically be notified of the update and download the new code. So the deployment process is two-part: 1. Bundle a mobile application with JS/HTML/CSS which talks to a server at foo.meteor.com 2. Run a server at foo.meteor.com. Whenever you push a new version of the application to the server, the mobile devices will download the new JS/HTML/CSS and refresh to run the new code. The server and mobile device "share persistent data" in the sense that the mobile device will eventually contain the same client code as the server.
- sgslo 12y agoAh, fantastic. Are collections that the mobile device subscribes to cached on the mobile device in any way?
- arbesfeld 12y agoLatency compensation works as usual, meaning that actions are immediately carried out on a local in-memory copy of the database, and then replicated to the server. There is no offline caching at the moment, but it's on our roadmap and there are some community solutions that you could try out.