XML Scalability

[PA]

Please help.
I am trying to create a scalabe web xml app. The majority of XML webpages,
examples, show data being formated and saved as an .xml file on the web server
and then rendered in the browser in some way (depending on browser). How
can this be scalable? What happens when 10,50,100 people are trying the
same thing at the same time?
Is there a scalable app architecture I havent seen? I would really like
to implement xml on a project Im working on.
Thanks in advance
PA

[Greg Longtin]

PA,

Sorry, but I kind of missing the point of your example. What happens if
10, 50, 100 people access a HTML page and associated CSS sheet at the
same time? Nothing but hardware will get around the problem of sending
data.

If by "show data being formatted and saved as an .xml file on the web
server", you mean some kind of data processing on the server on a per
client basis, I doubt anyone is doing that. The hit from saving every
request as a file is to burdensome. The newest MS ADO package allows
saving xml data as a stream (or string), and the newest xml preview
processor shows that MS is working on XSLT transforms being efficiently
done on the server. Last but not least, MS has the SQLXML preview
package that allows retrieving SQL Server data straight to XML.

Sorry for the obvious slant towards MS XML tools. That's what I work
with...

FWIW,

Greg Longtin

PA <PA@attachmate.com> wrote in message news:38fb505c$1@news.devx.com...
>
> Please help.
> I am trying to create a scalabe web xml app. The majority of XML
webpages,
> examples, show data being formated and saved as an .xml file on the
web server
> and then rendered in the browser in some way (depending on browser).
How
> can this be scalable? What happens when 10,50,100 people are trying
the
> same thing at the same time?
> Is there a scalable app architecture I havent seen? I would really
like
> to implement xml on a project Im working on.
> Thanks in advance
> PA

[PA]

Greg,
An example may be better. A client (ASP page) requests data. Using ADO
in the middle tier, data is requested from the db, formated as xml, and saved
as data.xml on the web server(?). The data.xml file is then rendered on
the client using xsl or css. How can you save .xml files on the web server
from two separate concurrent requests with overwriting, blocking, etc.?

Sorry if this is a simple question, just trying to understand. In the stream
option, is the xml stream sent to the client without the overhead of saving
a file on the web server? Where do you get the SQL xml package? Thanks
for the help
PA

"Greg Longtin" <longtin@att.net> wrote:
>PA,
>
>Sorry, but I kind of missing the point of your example. What happens if
>10, 50, 100 people access a HTML page and associated CSS sheet at the
>same time? Nothing but hardware will get around the problem of sending
>data.
>
>If by "show data being formatted and saved as an .xml file on the web
>server", you mean some kind of data processing on the server on a per
>client basis, I doubt anyone is doing that. The hit from saving every
>request as a file is to burdensome. The newest MS ADO package allows
>saving xml data as a stream (or string), and the newest xml preview
>processor shows that MS is working on XSLT transforms being efficiently
>done on the server. Last but not least, MS has the SQLXML preview
>package that allows retrieving SQL Server data straight to XML.
>
>Sorry for the obvious slant towards MS XML tools. That's what I work
>with...
>
>FWIW,
>
>Greg Longtin
>
>PA <PA@attachmate.com> wrote in message news:38fb505c$1@news.devx.com...
>>
>> Please help.
>> I am trying to create a scalabe web xml app. The majority of XML
>webpages,
>> examples, show data being formated and saved as an .xml file on the
>web server
>> and then rendered in the browser in some way (depending on browser).
>How
>> can this be scalable? What happens when 10,50,100 people are trying
>the
>> same thing at the same time?
>> Is there a scalable app architecture I havent seen? I would really
>like
>> to implement xml on a project Im working on.
>> Thanks in advance
>> PA
>

[Rohit Wason]

PA,
You're doing just a standard use of XML. In typical Database scenarios, XML
(instead of getting stored at WebServer) is built at run-time (using ASP).
The ASP, instead of returning a normal HTM o/p, returns XML format:
Response.ContentType = "text/xml"
<Employees>

<%While Not rs.EOF%>
<Employee>
<Name><%=rs!name%></Name>
<Age><%=rs!age%></Age>

[Greg Longtin]

PA,

> Sorry if this is a simple question, just trying to understand. In the
stream
> option, is the xml stream sent to the client without the overhead of
saving
> a file on the web server?

It can be. Critical issue is the move from ADO recordset to XML doesn't
require saving a file. ADO 2.5 --

http://www.microsoft.com/data/download_250rtm.htm


> Where do you get the SQL xml package?

http://msdn.microsoft.com/workshop/x...qlxml_prev.asp

and the newsgroup -

microsoft.public.sqlserver.xml

HTH,

Greg Longtin

[Greg Longtin]

Rohit,
If you can use it (MSFT XML Preview), you might find it faster using
XSLT to transform the XML returned by ADO 2.5 into more 'normal' XML.

FWIW,

Greg Longtin

Rohit Wason <rohitw@futuresoftindia.com> wrote in message
news:38fd782e$1@news.devx.com...
>
> PA,
> You're doing just a standard use of XML. In typical Database
scenarios, XML
> (instead of getting stored at WebServer) is built at run-time (using
ASP).
> The ASP, instead of returning a normal HTM o/p, returns XML format:
> Response.ContentType = "text/xml"
> <Employees>
>
> <%While Not rs.EOF%>
> <Employee>
> <Name><%=rs!name%></Name>
> <Age><%=rs!age%></Age>