XML.orgXML.org
FOCUS AREAS |XML-DEV |XML.org DAILY NEWSLINK |REGISTRY |RESOURCES |ABOUT
OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Re: [xml-dev] Bad Design? An XML Schema that forces applications tomaintain state

Roger writes:

> In other words, the XML Schema forces applications to maintain state.

Not exactly: applications that do not need to use that datum do not need to store for that elided value.

And it may be that the value of that datum is not its particular value at any time, but that the value has changed: e.g., when we are fighting, we don't want to continually check "are we still fighting?" but we do want to be buzzed when it "FINISHED".

In any case, there is no general principle that maintaining state is harmful: REST is an approach suited for (generating and implementing) specific architectures and use-cases, in particular, for highly-scalable server farms, but not every computer-to-computer communication fits in with this.

Regards
Rick

 



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


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

Copyright 1993-2007 XML.org. This site is hosted by OASIS