Hi Andreas. I don't put httpGate behind Apache since I don't need to use port 443, in any case without that websocket proxy module I'm not sure it would even be possible.
Yes, making those two numbers configurable is probably a good idea and trivial to implement, will fix that asap. On Sun, Jul 13, 2014 at 10:00 PM, <andr...@itship.ch> wrote: > Hi Henrik > > Thank you for publishing your work and the nice write up! > I will definitively study it in detail and probably reuse it at some > point in the future. > > About 1.) and 2.): I think this is highly depended on the actual use case, > and has to be configured individually for actual applications (e.g. when > the usual message interval is high, ping is probably not necessary). > Good you pointed this configurations out! > > One question: You write you use this in a LAMP environment, am I correct > in assuming clients connect directly to httpGate and then pl-web? > Or do you put httpGate behind Apache, and if so, why? > > Thanks :) > >> The past few days I've been working on websockets and the write up is >> here: http://picolisp.com/wiki/?Websockets >> >> There are two settings that could be discussed right away on this mailing >> list: >> >> 1.) The appropriateness of clearing out disconnected clients from the >> tag and id lists every 5 seconds, maybe it should be higher, maybe >> lower. >> >> 2.) The appropriateness of sending a ping from each client process to >> each client every 10 seconds to keep the connection alive, it could >> probably be higher. >> >> Finally note that I'm not using the words "subscribe", "publish" or >> "channel" in the post (or the code) is that I don't want to confuse >> what I've done with WAMP: http://wamp.ws/ since it's not an >> implementation of that sub-protocol. >> >> Enjoy! >> -- >> UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe >> > > > > -- > UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
