On Thu, May 29, 2014 at 5:26 PM, Tom Fennelly <[email protected]> wrote:
> > AFAIK... any proxy/gateway between the websocket client and server needs > to be pretty much websocket aware. SSE would seem like a perfect fit for > Jenkins since the client is listening only (not sending back to the server > - could implement that on top anyway if needed). As far as I know SSE is a > fancy long poll/comet style protocol and so would require the same > considerations re number of concurrent users. > > -- > > Happy to be proven wrong but I expect that even for the heaviest users of jenkins (masters) - the number of concurrent users couldn't be more than in the hundreds - mostly that will work without any web framework contortions (happy to be proven wrong). The biggest risk for websocket, as I see it, is the temptation to built in a real time chat client, and perhaps webrtc video conferencing (you broke the build - someone can instantly berate you via webrtc video feed). Terrible idea forget I said it ;) -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
