"we need ability to sequentially (not concurrently) process a second HTTP POST request"
The first part of this sentence says sequentially (not concurrently), but the description in the second half describes concurrent behavior. So which is it? Joakim Erdfelt / [email protected] On Tue, Jul 23, 2019 at 10:47 AM Joakim Erdfelt <[email protected]> wrote: > Standard HTTP/1.1 has persistent connections. > > The requests are processed in the order they are received. Sequentially. > The responses are returned in the order they are processed. Also > Sequentially. > > Joakim Erdfelt / [email protected] > > > On Tue, Jul 23, 2019 at 10:45 AM Sergey O <[email protected]> wrote: > >> Hello, >> >> Is it possible to implement server which supports some kind of the >> BOSH protocol (http://xmpp.org/extensions/xep-0124.html) with jetty? >> Particularly, we need ability to sequentially (not concurrently) process >> a second HTTP POST request before response on a first one is sent. Both >> requests should use the same persistent connection. >> If it is not possible to start the second request processing prior to >> response on the first one is sent, is it possible to receive notification >> about the second request availability? >> >> Best regards, >> Sergey >> _______________________________________________ >> jetty-users mailing list >> [email protected] >> To change your delivery options, retrieve your password, or unsubscribe >> from this list, visit >> https://www.eclipse.org/mailman/listinfo/jetty-users > >
_______________________________________________ jetty-users mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jetty-users
