Thank you!
On Mon, Feb 3, 2014 at 4:25 PM, Tony Wilk <[email protected]>wrote: > Hi, > I've put a couple of articles on codeproject which may be of interest: > > Using-Sec-Websocket-Protocol<http://www.codeproject.com/Articles/716148/Using-Sec-Websocket-Protocol> > and > JSONsvc-a-proxy-peer-peer-protocol-for-Websockets<http://www.codeproject.com/Articles/718059/JSONsvc-a-proxy-peer-peer-protocol-for-Websockets> > > re: Mongoose... > The websockets interface doesn't currently support Sec-Websocket-Protocol; > it may be useful if it did. > I don't think Mongoose should handle Sec-Websocket-Protocol header, it should be up to application that embeds Mongoose to reply with the correct header. Or do you think otherwise? Please let me know! > I notice mg_connection has a void *connection_param which is good for > keeping track of persistent connections like websockets > Yes, connection_param is meant to do exactly that: to keep a connection-specific state. -- You received this message because you are subscribed to the Google Groups "mongoose-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/mongoose-users. For more options, visit https://groups.google.com/groups/opt_out.
