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


Help: OASIS Mailing Lists Help | MarkMail Help



   RE: [xml-dev] Web Services Best Practice, summary 2

[ Lists Home | Date Index | Thread Index ]

I agree that one can aggregate that way.  

Or, depending on how close to real time you need that 
data, maybe these services should wake up in the off 
hours (whatever those are in your geo-temporal-social 
location), get all the data it needs for that day in 
one coarse transaction, copy it to the local node, 
and process it.  How are rates being charged for using 
the service?  How binding are the contracts for the 
goodness of the service and the information it provides?

One can go in either direction and aggregation is one 
way to do it.  So is replication.  There are issues 
that go beyond the speed of the network.


Scary stuff when it is applied from shrinkwrap to naked 
real-time transactions.

Or this:  How the Web Was Lost
(This is rated R: for language)


From: Amy Lewis [mailto:amyzing@talsever.com]

I'm not entirely sure that I agree with these best practices, although
they are likely to be good rules of thumb.

Consider this scenario:


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS