[
Lists Home |
Date Index |
Thread Index
]
> "The main point here is there is almost an order of
> magnitude between straightforward Web services using XML encoding and an
> implementation that takes care of binary encoding." They're also going to
> have a "Fast Infoset" and "Fast Schema".
Too many folks seem to want such optimizations, and choose to use them, too
early in a project cycle. "Premature optimization is the root of all evil"
syndrome.
First, they should architect and build their app using XML technologies which
is a cost effective and less expensive way to get a project out the door fast
(as others have pointed out). Then they should review their
architecture/design/code and do some refactoring. Then, and only if you need
to, look at what optimizations might be required. Many times that is "good
enuf" and no more need be done.
Availability of binary formats leads to temptation to prematurely optimize,
which will get people into more hot water than taking a more standards-based,
straightforward approach. But it does sell more software by the proprietary
behemoths.
All my NSHO.
Then again, common sense isn't....so hang on. It will be an interesting
ride.
Andrzej Jan Taramina
Chaeron Corporation: Enterprise System Solutions
http://www.chaeron.com
|
