Alternative Web Services Architectures BOF
by Sam Ruby
Don Box commented that
"If it takes three minutes for a response, it is not really HTTP any
more". In situations where responses may take five days, is it
possible to apply the architectural style that made the web so successful, or is
a new approach required? Put another way, is REST tightly bound to HTTP or
can the architectural principles it embodies be applied to other protocols?
When the request and response are sufficiently temporally separated, one
essentially end up with the equivalent of UDP datagrams. Is it possible to layer
on the equivalent of what TCP provides in terms of error recovery, flow control,
and reliability in such a context?
The REST wiki suggests
that the REST architectural style is most closely related to that of TupleSpaces.
One important difference is that in TupleSpaces the sender does not identify the
recipient. Data is addressed and routed based on content. Is there a
place for such a model in "Alternative Web Services Architectures"?
BOF topic - long lived conversations
I think talking about whether REST applies to long lived conversations would be a great topic.
There has been discussion about this on the REST forums, but it would be good to go over it again.
SOAP vs. REST Resources
I've started a SOAP vs. REST Resource page:
REST Protocol Alternatives
"can the architectural principles it embodies be applied to other protocols"