Can HTTP eWay support simultaneous end users?

[johnvanderwood]

My company's product provides an HTTP/XML API. We are considering integration with SeeBeyond by way of the HTTP(S) eWay. We would keep a single session open between our web server and SB, using the eWay as a sort of concentrator for many end users.

But... will this eWay cause requests to be queued and handled in a single-threaded request/response way (bad)? Or will it have a pool of threads/sockets that enables multiple simultaneous requests (good)?

Apologies to SeeBeyond jocks if this is a dumb question - I have looked through the HTTP eWay doc and did not get a clear answer. Thanks,

John Vanderwood

 

[essive]

I assume you're speaking about using SeeBeyond's HTTP eWay as a client NOT as a server. You must have a web server in front of SeeBeyond in order to use it as a HTTP server. If you are using the HTTP eWay as a client you must use the Java eWay Connection with a MultiMode eWay to get the benefits you desire. You can thread within JVMs with multiple collaborations or have multiple JVMs for outbound HTTP requests or posts. You do not really get a thread pool in the way you are thinking.

If you are using a web server in front of SeeBeyond as a HTTP server then you use either the MUX eWay or JMS from the web server to SeeBeyond. Both can thread but there are limits. You should really think of SeeBeyond being a fixed-scaled environment. You decide the scale and build to it. It is not really a dynamically scaled environment.

 

[johnvanderwood]

Thanks essive... yes I meant using SeeBeyond as a client. Your answer was what I needed to know.