From: Love, J. <Jay...@us...> - 2001-01-30 15:06:29
|
That's what we're going to end up with. If you are using the Async AppServer, it will be just as you have described, your app will write to HTTPRespose.out, or something like that, and as long as you have already told HTTPResponse to send the headers, your data will be sent at the next opportunity, and the call will not block. If you are using the plain Threaded AppServer, then the call will block until the data can be sent. If you are using cgi, it won't blobk and the data will be immediately written to stdout. I don't know that we need all of the other Medusa tools. Tell me what you'd like besides being able to write to a file like object and know that the data will be sent ASAP and won't wait until your servlet is completely done and won't block execution. Jay -----Original Message----- From: Terrel Shumway [mailto:tsh...@tr...] Sent: Tuesday, January 30, 2001 9:57 AM To: Love, Jay Cc: 'web...@li...' Subject: Re: [Webware-discuss] AppServer Communications "Love, Jay" wrote: > Ideally, we want to have the sending stream that servlets write to be a > buffered object that is written to, and optionally the data can be sent as > it is written. The same technique could be used for receiving input data, as > you have asked. This will not be terribly difficult to do, I just haven't > gotten to it yet. > How difficult would it be to expose all of the medusa tools (producers, continuations, et. al.) and make things asynchronous throughout? I would like to be able to say: "here is what I want done, I don't care how or when you do it." I realize that it is a model most people are not familiar with. Maybe we could create a class such as AsyncServlet.... servlet.write would map to channel.push. Hmm... how does one do an asynchronous SQL query? My ignorance is showing. Sendfile is an obvious application, but anything that requires computation requires a lot of work to break it up. I need to play with this some more. -- Terrel ---------------------------------------------------------------------------- This e-mail and any attachments may be confidential or legally privileged. If you received this message in error or are not the intended recipient, you should destroy the e-mail message and any attachments or copies, and you are prohibited from retaining, distributing, disclosing or using any information contained herein. Please inform us of the erroneous delivery by return e-mail. Thank you for your cooperation. ---------------------------------------------------------------------------- |
From: Terrel S. <tsh...@tr...> - 2001-01-30 16:49:21
|
"Love, Jay" wrote: > That's what we're going to end up with. If you are using the Async > AppServer, it will be just as you have described, your app will write to > HTTPRespose.out, or something like that, and as long as you have already > told HTTPResponse to send the headers, your data will be sent at the next > opportunity, and the call will not block. If you are using the plain > Threaded AppServer, then the call will block until the data can be sent. If > you are using cgi, it won't blobk and the data will be immediately written > to stdout. > This is the right model. > > I don't know that we need all of the other Medusa tools. Tell me what you'd > like besides being able to write to a file like object and know that the > data will be sent ASAP and won't wait until your servlet is completely done > and won't block execution. I guess what I like is the sendfile functinality: "Here is a file: send it. Then, when you're done, send this" I think I am thinking of other applications: chat and file servers, not servlets. |
From: Chuck E. <ec...@mi...> - 2001-01-30 17:33:48
|
At 07:54 AM 1/30/2001 -0800, Terrel Shumway wrote: >I guess what I like is the sendfile functinality: "Here is a file: send it. >Then, when you're >done, send this" > >I think I am thinking of other applications: chat and file servers, not >servlets. In addition to Vlk's later suggestion of using the Refresh: header, would the proposed TaskKit discussed earlier cover your needs? -Chuck |
From: Terrel S. <tsh...@tr...> - 2001-01-31 05:58:27
|
Chuck Esterbrook wrote: > At 07:54 AM 1/30/2001 -0800, Terrel Shumway wrote: > >I guess what I like is the sendfile functinality: "Here is a file: send it. > >Then, when you're > >done, send this" > > > >I think I am thinking of other applications: chat and file servers, not > >servlets. > > In addition to Vlk's later suggestion of using the Refresh: header, would > the proposed TaskKit discussed earlier cover your needs? > > -Chuck What I am thinking of is more of a full-service groupware suite: Mail, news, file-sharing, version control, document management, whiteboard, chat, etc. Yes, it is amazing what looks like a nail when HTTP is your hammer--much of this can be done in a browser. However, I would rather not constrain the usability by excluding other protocols. I do intend to make good use of Python and webware, but it is an application more than a "weblication" |