OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

wsia message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Subject: [wsia] Current Journalism: XML.COM article on Web Services

Hi Folks,

This article came up on the xml-dev list, so I read it and I am 
passing it along.


I think that Rich's suggestions in the Embedded Use-Case for 
wsia-specific terminology address some of the issues in the 
typing/coupling choices we need to make, or for which we need to 
provide. However, we have cases that need the entire range of strong 
to weakly typed and tightly to loosely coupled AND static synchronous 
(short, specific, immediate single-packet) to dynamic (long, 
intermittent, streaming, changeable-stateful) messaging exchange 
patterns. THAT's a lot to chew on. I suppose the question that is 
nibbling at me is, do we need to chew on all of it at once?

We have broken our use-cases down (somewhat) into levels of 
complexity. Should we start by working on the simpler LCD spec 
requirements first and start writing spec on that while continuing to 
explore the more complex issues? What concerns me is that we may get 
rather further along in writing spec than the underlying structure 
can support at present. I have a feeling that harvesting some 
low-hanging fruit soon might influence the on-going debates about 
HTTP, SOAP, etc. I have had the notion in my head for a while that we 
might want to look at more than a single messaging transport 
protocol, and see if such an arrangement would be amenable to 
synchronization and integration with HTTP, SOAP, et al, and still be 
deliverable in protocol/device independence.

Maybe I just like to worry, eh?


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Powered by eList eXpress LLC