Hi John,
John said:
I am really interested in using more XML for data deliver on public sites.
It has proven to be very useful for us in storing and delivering
hierarchical data. But, for deliver to a browser, other than IE5, I would
need to implement a server-sided XSL processor to convert XML --> HTML. I
wrote one 2 years back, back when MS had only a crappy non-working beta.
Mine, would not be acceptable for a high-hit environment. But, I can tell
you I will need quite a sales pitch to buy someone else's right now instead
of just improving our own.
Didier replies:
>From your comment may I deduce that the application you refer to is not to
perform EDI but more to prepare XML documents for renditions. If that is the
case, since we are developing a high performance XML server here are what we
discovered so far:
- MSXML3 is quite fast if you use the template caching mechanism
- If the XML server is to be running on a SMP machine (higher than 2
processors) then, A big difference in performance is obtained by allocating
a separate heap for each thread. Any solution where threads are sharing a
single resource, the heap, will have decreased performance for a huge number
of simultaneous hits.
- You gain a lot by clustering servers and using load balancing mechanism.
Several sites with bit hits are using server farms.
- In the case when you have to provide multiple rendering formats like WML,
HTML and VoiceXML to only name a few. Then, you gain a lot by having a very
fast pattern recognition algorithm to recognize the user agent and built a
device profile for it and allow the style sheets to get access to the device
profile to better adapt to the requesting device. For WML, HTML and VoiceXML
there are actually more than 600 different user agent to be recognized.
- The server has to support local dynamic XML creation with script
languages, Java or objects created with compiled languages. Thus, the web
component dynamically creates the XML document and this latter is further
transformed into the proper rendering language. So the pipeline process
should be as efficient as possible and should allow a caching mechanism at
each stage to accelerate the process.
So, these are the elements, just to name a few, that have to be considered
for a high performance XML server.
Cheers
Didier PH Martin
----------------------------------------------
Email: [EMAIL PROTECTED]
Conferences: xml devconf 2000 (http://www.xmldevconf2000.com)
Book: XML Professional (http://www.wrox.com)
column: Didier's labs (http://www.xml.com)
------ XML/edi Group Discussion List ------
Homepage = http://www.XMLedi-Group.org
Unsubscribe = send email to: [EMAIL PROTECTED]
Leave the subject and body of the message blank
Questions/requests: [EMAIL PROTECTED]
To receive only one message per day (digest format)
send the following message to [EMAIL PROTECTED],
(leave the subject line blank)
digest xmledi-group your-email-address
To join the XML/edi Group complete the form located at:
http://www.xmledi-group.org/xmledigroup/mail1.htm
