Gervas, > (1) A significant impediment > (2) Somthing we just have to live with > (3) does not really matter given the computing > horsepower and network bandwidth commonly available?
In some ways these questions are being addressed on multiple fronts. There are folks who are throwing hardware at the problem (e.g. XML Security Gateways) to offload XML processing from software to hardware and achieve significant increase in perf. The there are the folks who are looking at alternate encodings for XML ( I had at one point written about it and what the promises and issues with it are in the current timeframe) @ http://www.aniltj.com/blog/2006/10/29/BinaryXMLWebServicesAndStandards.a spx Alternate Url: http://tinyurl.com/365unl I do think that in some ways the most critical thing that a lot of folks seem NOT to do is to tackle this at the service design stage itself: - Do you REALLY need to deliver all of this info to the client? - Can this operation be performed in an asynchronous manner? - Are you doing performance engineering end-to-end (i.e. If the biggest application bottleneck is in the business logic processing or the database backend and not in the XML processing itself, are you looking to optimize where it makes the most sense, instead of looking purely at the XML perf?) Regards, - Anil :- :- Anil John :- http://www.aniltj.com/blog/ :-
