Having a sender using a unidirectional transmit-only link add a
Connection: cannot-hear-response
or similar header to its PUT request as a warning to the receiver
seems straightforward.
Of limited utility, in very rare unusual situations.
On 8 Jun 2009, at 14:55, Joe Touch wrote:
Lloyd Wood wrote:
...
use of PUT gets around the initial request and response for long-
delay
links.
...
again, PUT allows that. The responses (if any - I can see a case for
blind unidirectional PUTs) get daisy-chained into the persistent
pipeline going the other way.
It's easy to implement PUT without a response.
http-over-dtb PUT-request.txt >> /dev/null
A return response code (succeed/fail) is required, or this isn't HTTP
anymore.
DTN work: http://info.ee.surrey.ac.uk/Personal/L.Wood/saratoga/
<http://info.surrey.ac.uk/Personal/L.Wood/><[email protected]>
