mrauhu/meteor-clusterws

Guide for adding support of 🚀 ClusterWS in the Meteor

meteor-clusterws's Issues

Problem updating to Meteor 1.11

Hello, I got these error messages when I ran meteor update inside my project folder:

=> Errors while initializing project:

While selecting package versions:
error: No version of ddp-server satisfies all constraints: @=2.3.1, @~2.3.2
Constraints on package "ddp-server":
* ddp-server@=2.3.1 <- top level
* ddp-server@~2.3.2 <- top level
* [email protected] <- ddp 1.4.0 <- accounts-base 1.7.0

No version of socket-stream-client satisfies all constraints: @=0.3.0, @~0.3.1
Constraints on package "socket-stream-client":
* socket-stream-client@=0.3.0 <- top level
* socket-stream-client@~0.3.1 <- top level
* [email protected] <- ddp-client 2.3.3 <- ddp 1.4.0 <- accounts-base
1.7.0

Please stop using my trademarks

I believe I've told you before,

This thing is using a three year old fork (legally a derivative work) that is not "uWebSockets". They call it cWS, the fork, and so should you. The fork in question is not the original work and per license terms must not be misrepresented as being the original thing. Remember that you're licensing my IP as per my terms, and I'm currently not happy with how you mix the two projects.

Please change naming and headers to clearly and accurately refer to this "cWS" thing instead.

Also I would not like to be listed under "thanks to".

Problem while installing

Hi, I tried to grok it but I can't, I get this error when I come to the point in the docs to install the stream-server-uws - package:

> meteor add stream-server-uws

This project is already at Meteor 1.10.2, the latest release.
=> Errors while upgrading packages:

While selecting package versions:
error: No version of socket-stream-client satisfies all constraints: @=0.2.3, @~0.3.0
Constraints on package "socket-stream-client":
* socket-stream-client@=0.2.3 <- top level
* socket-stream-client@~0.3.0 <- top level
* [email protected] <- ddp-client 2.3.3 <- ddp 1.4.0 <- accounts-base 1.6.0 <- accounts-password 1.6.0
* [email protected] <- ddp-client 2.3.3 <- ddp 1.4.0 <- accounts-password 1.6.0

Question: How to switch to meteor-uwebsockets smoothly (in a Cordova App)?

Hi, while testing the meteor-uwebsockets implementation I ran into the following issue (I think):

When I updated the server version, desktop-clients would work fine after a reload (or maybe even did the hot code push update alright, I'm not totally sure).

But my cordova-app, which was built containing the previous version of my app, wouldn't connect to the updated server to download the new client it seems?

I got some messages on the cordova apps' console about CORS / Invalid access / headers to the local server (which runs within the cordova app to server the actual files of the app to the cordova webview).

Now when I rebuilt the entire app with the new source code included everything seems to work fine.

But of course the issue is, when I want to update to the new code, my existing customers won't be update via HCP, and even if I go the "long way" through the app store it's not clear when everyone will have updated, and that means that some customers might look at an app which is stuck at the loading screen, which isn't good.

---

Do you have any Idea how I could mitigate this maybe? Is it possible to first deploy only the client part, without updating the server for example? Then I could monitor the installed apps "in the wild" and update them in a two-step process.

Thank you again for your effort.