[prev in list] [next in list] [prev in thread] [next in thread] 

List:       uwsgi
Subject:    [uWSGI] Initiating a websocket connection
From:       manchev () bin ! bz (manchev at bin ! bz)
Date:       2014-03-30 15:37:41
Message-ID: 20140330153741.GA8277 () govnarci
[Download RAW message or body]

I thought that websockets will be more performant in this case exactly because the \
connection is never closed (or rather should be kept alive) - i.e. no  connection \
overhead every time a message needs to be passed.

With thousands of messages passed between nodes I thought it would make a real \
difference between websockets and rpc, but that might not be the case as I have  not \
tested this assumption.

In any case - rpc+ssl client support would be just awesome for my purposes.
Looking forward to seeing a working implementation that I can test and benchmark.

Thanks for the heads up and the great work Roberto!

On Sun, Mar 30, 2014 at 07:57:49AM +0200, Roberto De Ioris wrote:
> 
> > Hi guys,
> > 
> > Is there any way to initiate a websocket connection with the uwsgi API
> > to another uwsgi instance?
> > 
> > Here's my use case:
> > - there are several nodes that I need to talk to each other
> > - some are only receiving messages, others only generating/sending them
> > and some of them do both
> > - a secure and low-latency solution is needed as there are thousands of
> > small messages passed between the nodes in an untrusted environment
> > 
> > So I figured websockets over https are a good start as they fit the bill.
> > 
> > I looked at the RPC stack but I don't think it will work because:
> > - it can't provide the security I need (at least I don't see how)
> > - while it's fast I guess websockets will do better due to the number of
> > messages passed
> > 
> > I guess my assumptions might be wrong, but any possible solutions are
> > appreciated in any case.
> > 
> > 
> 
> the best solution would be having rpc+ssl client support (server support
> is already implemented).
> 
> I will investigate on it.
> 
> I do not think websockets are a good approach, you need to hold the
> connection opened for the whole request, manage ping pong and so on...
> 
> 
> -- 
> Roberto De Ioris
> http://unbit.it
> _______________________________________________
> uWSGI mailing list
> uWSGI at lists.unbit.it
> http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi


[prev in list] [next in list] [prev in thread] [next in thread]