On 4/13/06, Jan Algermissen <[EMAIL PROTECTED]> wrote:
> I still have not seen an explicit list of the enterprise class
> problems HTTP cannot handle. Maybe I missed that list, but IIRC,
> everytime this claim has been it has not been 'backed up' with a list
> of undoable things.
If you don't stumble over them in your domain, you probably don't have
to worry about them. :-) If you do stumble over them in your domain,
you are probably too busy fighting fires and phishers and intruders
and pleading with the CFO to get budget for more app server racks to
hang out on this list. <duck>
But the canonical list is probably the -ilities covered by WS-*
(except for the infamous WS-Transfer of course). Multi-hop Reliable
messaging, single sign on authentication / authorization, transaction
management, etc. etc. etc. Contrary to popular belief, people don't
dream up these things to make work for themselves. But that's another
permathread.
For T/J/X-Spaces, the main limitation of HTTP that I know of is the
lack of a standard associative lookup / query mechanism.
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/service-orientated-architecture/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
