Davanum, et al, I took at the first stub at the rewrite of the SimpleHTTPServer
On Thu, 2006-05-18 at 11:07 -1000, Chuck Williams wrote: > Thanks Oleg. I'll exercise your code, report issues, provided patches, > etc., as soon as it is available. > > I need some features that might not be available in a simple > implementation, primarily the ability to control a set of thread pools > assigned to different operations. E.g., I've got a bunch of quick small > operations and a few big slow ones. I need to limit the processing of > the large ones so that reading and processing the incoming messages does > not run the jvm out of memory or cause performance issues, while > allowing the small ones to get through at high priority. In general, > I'd like to be able to control the allocation of incoming messages to > threads in operation-dependent thread pools, limit the threads in the > each pool, and relatively prioritize the pools. > > This might have architectural implications has the dispatching needs to > be done to determine the operation and thereby select the thread pool. > It is essential that the reading of messages be performed by the axis2 > message receivers so the large ones can be streamed through. Ideally, > the sizes of the thread pools could be varied dynamically, so that for > example a particularly large message could prevent other threads from > being assigned until it completes; however, I can provide the dynamic > size-based resource control in the app even with fixed size thread > pools. Even without operation-based thread pools, so long as the > messages are not read by the http client, I could implement this > mechanism as a secondary thread assignment in the app. > > I'd be happy to add support for this kind of functionality if not part > of the core package. > > Chuck > > > Oleg Kalnichevski wrote on 05/18/2006 10:54 AM: > > Chuck Williams wrote: > >> > >> robert burrell donkin wrote on 05/18/2006 07:56 AM: > >>> On 5/18/06, *Davanum Srinivas* <[EMAIL PROTECTED] > >>> <mailto:[EMAIL PROTECTED]>> wrote: > >>> > >>> <snip> > >>> > >>> The long term plan is to use HttpCore in HttpComponents. See > >>> thread: > >>> > >>> http://marc.theaimsgroup.com/?l=axis-dev&w=2&r=1&s=httpcomponents&q=b > >>> > >>> <http://marc.theaimsgroup.com/?l=axis-dev&w=2&r=1&s=httpcomponents&q=b> > >>> > >>> > >>> +1 > >>> > >>> this will happen all the more quickly if contributors step up and > >>> lend a hand. > >>> > >>> chuck - sounds you like you have a real itch: want to help us > >>> scratch it? > >> Yes, I do. Unlike some others on the list, I need to deliver a > >> robust product using axis2 in just a few months. I chose axis2 > >> because of its architecture, basis in stax, support for streaming, > >> and position to be the Java soap platform of the future, but I need > >> to make my use of it solid now. I have a dedicated soap service > >> component and definitely want to use a thin built-in http server > >> rather than say a full tomcat installation. > >> > >> Robert, are you connected with HttpCore? Do you know if I could grab > >> it now and create a replacement for SimpleHTTPServer and friends > >> based on it? Are there others with a similar need now who want to > >> coordinate/collaborate? I don't mind fixing some bugs or adding a > >> few features along the way, as I'm doing with axis2. > >> > >> Chuck > > Chuck, > > > > You can find some info on the HttpComponents project here: > > http://jakarta.apache.org/httpcomponents/index.html > > > > I'll throw together a drop-in replacement for SimpleHTTPServer based > > on HttpCore this weekend and post a patch against Axis2 SVN trunk. > > Essentially this is all it takes to create a simple HTTP server based > > on HttpCore: > > http://svn.apache.org/repos/asf/jakarta/httpcomponents/httpcore/trunk/src/examples/org/apache/http/examples/ElementalHttpServer.java > > > > > > It will be hugely appreciated if you could help me test it and see how > > well (or badly) it fares. > > > > Mind you, HttpCore is still an early ALPHA. We are not prepared to > > freeze the API yet. However, it is very much the proverbial chicken > > and egg situation: the more people start testing HttpCore in real life > > applications and give us feedback the sooner we can finalize the API > > and stabilize the code. > > > > Cheers, > > > > Oleg > > > > > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [EMAIL PROTECTED] For > >> additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
