ddp

So I have some things in my application that I don't need an immediate reactivity and found out about properties pollingThrottleMs and pollingIntervalMs in the documentation. So here is basically all the information about those properties I managed to find: pollingIntervalMs Number (Server only) How often to poll this query when observing on the server. In milliseconds. Defaults to 10 seconds. pollingThrottleMs Number (Server only) Minimum time to allow between re-polling. Increasing this will save CPU and mongo load at the expense of slower updates to users. Decreasing this is not recommended

I'm developing a Meteor application with two client, one is in JavaScript and the other one is in C. I'm actually trying to connect my C app to the server using websocket. I'm using the library nopoll for the websocket ( http://www.aspl.es/nopoll/html/index.html ) and jansson for the JSON serialization ( http://www.digip.org/jansson/ ). I read the DDP Specification ( https://github.com/meteor/meteor/blob/devel/packages/ddp/DDP.md ) and this brief (but good) explanation ( https://meteorhacks.com/introduction-to-ddp.html ). Here is the code is the websocket initialization int main(int ac, char**

I have a Meteor app which runs on a local server for developement ( http://10.0.2.10:3000 ). The ROOT_URL is set correctly so __meteor_runtime_config__.ROOT_URL equals this URL. Of course the app is working perfectly fine in the browser on a client computer within 10.0.2.0/24. The app is also working fine on mobile chrome/firefox on my android cell phone which is also part of 10.0.2.0/24. However when I try to run it as app on this cell phone with meteor run android-device --mobile-server http://10.0.2.10:3000/ something strange happens: When the app starts for the first time (or the first

I have a Meteor app A and another application B , not using Meteor, but making some data exchange with the app A . It works fine when I launch A on a machine in my local network, but when I deploy it on meteor.com hosting it doesn't. Server doesn't reply. B uses code new WebSocket("ws://" + host + ":3000/websocket") for connection (DDP protocol). But when I change ws to wss it doesn't work any more even with the machine in LAN - it doesn't reply. I saw that main page of app A when I open it in browser uses URLs like wss://ddp--6774-{my host name}.meteor.com/sockjs/465/asf0b7da/websocket .

meteor uses DDP over socks / websockets. How do i get any type of view of what's going on in the browsers debug console? In the network panel of chrome at least there is just a single "websocket" connection without much info on the traffic running over it. I'm aware of arunoda's DDP analyzer and proxy but was looking for other ways to get basic information on traffic. I would have thought chrome's debugging tools would have a bit more support for protocols other than HTTP, and interested to know what else others find useful. You could try logging the messages as a simple starting point.