Websockets: wait or implement now?

[Johnny Luong]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Have you tried IceStorm?

http://doc.zeroc.com/display/Ice/IceStorm

As far as WebSockets go, if you control both ends of the communication,
then it doesn't really matter if you using a draft of the protocol or not.

- -Johnny

On 07/01/2011 12:31 PM, Norman Maurer wrote:
> Did you also checkout hazelcast ? It also support clustered
> notification systems etc:
> 
> http://www.hazelcast.com/documentation.jsp#Events
> 
> Bye,
> Norman
> 
> 2011/7/1 Jeff G. <jeff at steelhouse.com>:
>> I'm building a cluster system using netty for part of the networking, as well
>> as a client library for the cluster system (it's a storage cluster), and I
>> want to build in a mechanism to push notifications to clients if the cluster
>> topology changes.  I initially tried using ActiveMQ to do a pub/sub
>> mechanism, but I've run up against a wall where clients in different
>> networks can't subscribe to the topic (ActiveMQ is redirecting the clients
>> to the private IP of the server it's on instead of allowing them to connect
>> via the public IP, so connections are failing), so I'm thinking I'm not
>> going to waste any more time on the message queue (I've already wasted about
>> 3 weeks trying to make it work and have not had much success).
>>
>> Since websockets is still a draft, should I wait for that to finalize and
>> netty's support to be more complete, or it is safe to implement websockets
>> in the client and the server right now (this is a production system that is
>> also going to be licensed to third parties)?  Keep in mind that clients of
>> this system will not be running in browsers, so I have to be able to have
>> the cluster's client library be able to speak websocket if I do it this way.
>> My only other viable option is long polling, but I'd rather not have the
>> client lib create any more threads (the servers it runs inside already
>> create pretty much every thread in the known universe when they start up, so
>> my code gets close to starvation on initialization).  Alternatively, if
>> there's an idea I haven't though of yet, I'm open to suggestions.
>>
>> --
>> View this message in context: http://netty-forums-and-mailing-lists.685743.n2.nabble.com/Websockets-wait-or-implement-now-tp6538889p6538889.html
>> Sent from the Netty User Group mailing list archive at Nabble.com.
>> _______________________________________________
>> netty-users mailing list
>> netty-users at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/netty-users
>>
> 
> _______________________________________________
> netty-users mailing list
> netty-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/netty-users
> 
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iQIcBAEBCAAGBQJODjfqAAoJENQfv1FjsMMv8jwP/336GH5G89f39RdUDquy0Wme
Hcee88A0RA+UOB31wUXmeMHnWYVcWSrS8Va2QpmIKFu8hYyX6f3H6ldQHgsE95NA
8IDigy0pon4x3kQGJLre45W+1uwmLjD4D++3kkCUNbn0HEXzWZQOaff7iOfJ/Ai3
uRX8a8sObTIFPzI9SPJr2Qkws7I1zqacly1/VUulU7UNg6j5EzN8wWtIARf0ewlI
76WRZMUJ7FrnWf8EKq5JgsCCAnj3b4bR0DhN0CwxcPzrlJ/vSk9TU6USi619/IEJ
p5wbuLc2WIsrgvgW39Ztp0nGUv/dSEb1YB/jOWCqjbO/KljfU3HuNvsF1f9Z3mcV
HAtlNpRbqu8MrORLr17HuaHnMv/vqAKEp72zA+dRBa/wBercztPRsBV8iVP4IL9t
G2McFrBcGYUDbPva2OHNK99J9NZnNqsE31tgHwXaQ28odVEO3bket99FV9yo1PFM
rqqVS9qRLkR6z/NIutZzO1mpO1bPOH906Au1APpESMx4/HiUbsYsY8xlevKDakRV
qUDKgnUdAkhVvkVm5JiuEBkitbCfN9d4ASiR9vEZrsXCClYhnpau0nxsz+OVBuLZ
pJozLX5Y+vhX6it95STH/EonYCqqwTMBxBr7fV1dUT4iDmj8iWmZrY4TZMud9X8D
U+xU+XRYUAbxCIznwu2x
=7GK8
-----END PGP SIGNATURE-----