I have just realised what it is with this that bothers me :)
==== O/P from above example: ====
HTTP/1.0 200 Document Follows
MIME-Version: 1.0
Content-Type: text/html
Status: 10% done
Status: 20% done
....
==== O/P from above example: ====
In the case of what we are doing here, it would be nice to send back
these Status/Progress reports _BUT_ the search isnt sure of the correct
HTTP response code when it starts. The response code depends on the
results of the search. (eg: 200 is OK, 302 is a referal for correct
retrival later on, 40x is a failure etc.)
I cant quite see how this method would allow you to be alter the
response on the fly. The only way that I can see this scheme working
correctly would be to define a new status code that can be superceeded
in the header, like say:
==== O/P from example ====
HTTP/1.0 205 Status Information
MIME-Version: 1.0
Status: 10% done
Status: 20% done
Status: 30% done
Status: 40% done
Status: 50% done
Status: 60% done
Status: 70% done
Status: 80% done
Status: 90% done
Status: 100% done
HTTP/1.0 302 Found
Location: http://...../
MIME-Version: 1.0
....
==== O/P from example ====
But I can also see problems with this. :) So I cant see it being a
possibility for a lot of heavy DB usage, where you cant expect to know
you have a hit immediatly.
Actually looking at my copy of the HTTP spec I cant see anything that
says you cant alter the status code on the fly but I have a feeling that
it would break most if not all browsers :) :) :)
Anyone for HTTP/1.1 ? :)
Paul
.-------------------------------------------------------------------------.
|_______Paul_S._Wain,_(X.500_Project_Engineer_and_WWW/HTTP_chappie),______|
| Computer Centre, Brunel University, Uxbridge, Middx., UB8 3PH, ENGLAND. |
|___VOICE:_+44_895_274000_extn_2391_______EMAIL: [email protected] __|
| http://http2.brunel.ac.uk:8080/paul/ |
`-------------------------------------------------------------------------'