W3C home > Mailing lists > Public > www-talk@w3.org > September to October 2007

RE: How to handle errors if contents of response are dynamically generated?

From: Mike Dierken <dierken@gmail.com>
Date: Thu, 13 Sep 2007 20:57:41 -0700
To: "'Mark Baker'" <distobj@acm.org>, "'X. Long'" <xlong07@yahoo.com>
Cc: <www-talk@w3.org>
Message-ID: <000301c7f683$66b7aad0$0201a8c0@mercury>

How much data is buffered on the server?
If that dynamically generated can be stored (at least temporarily), a root
document with links to chunks/fragments can be returned quickly and each
chuck would be a separate request, with it's own response status code.


> -----Original Message-----
> From: www-talk-request@w3.org 
> [mailto:www-talk-request@w3.org] On Behalf Of Mark Baker
> Sent: Thursday, September 13, 2007 8:38 PM
> To: X. Long
> Cc: www-talk@w3.org
> Subject: Re: How to handle errors if contents of response are 
> dynamically generated?
> 
> 
> On 9/13/07, X. Long <xlong07@yahoo.com> wrote:
> > Thanks Mark! The HTTP server I am building is a server that provide 
> > dynamic data (format can be binary or text, size can vary 
> from MB to 
> > TB) according to requests of users. The server is supposed to serve 
> > user scripts (e.g., in
> > perl/python/java/c#) and browsers (e.g., ie).
> 
> Hmm, that kind of generality means you need a very general solution.
> I'm not aware of a single solution which would meet your needs.
> 
> Had you said that you were using just one or two specific 
> data formats, then you might consider injecting an extension 
> into the data that signalled the error (if the format 
> supported that, plus with some script that could render it in 
> a browser).  That doesn't sound general enough for you though.
> 
> > The expected solution would be the client can get aware of 
> the error 
> > immediately (not waiting for timeout and knowing the data 
> is incomplete).
> > Ideally, users should be notified this is an internal error 
> and they 
> > should contact admin instead of repeating the request.
> >
> > Also, since this is a well known problem with HTTP, what are the 
> > general approaches recommended? It will be great if some previous 
> > discussions about this topic can be pointed to me.
> 
> It's well known, but not so oft-encountered AFAIK.  You might 
> try digging through the IETF HTTP WG archives at 
> http://lists.w3.org/Archives/Public/ietf-http-wg/
> 
> Sorry I couldn't be more help.
> 
> Mark.
> -- 
> Mark Baker.  Ottawa, Ontario, CANADA.         http://www.markbaker.ca
> Coactus; Web-inspired integration strategies  http://www.coactus.com
> 
Received on Friday, 14 September 2007 03:57:41 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 10 December 2014 20:08:13 UTC