This is the mail archive of the
xsl-list@mulberrytech.com
mailin st .
RE: Which one to choose
- To
- Subject: RE: Which one to choHjÂ:/L
- Fro t;
- Date: Wed, 16 Feb 2000 09:33:30 -0000
Reply-To: xsl-list at mulberrytech dot com
SQL 7 also has an XML plug-in which allows you to store SQL queries ML
format and automatically output the results of that query in a well formed
XML. It is said to be much faster than ASP + C and seems to be fairly
stable when we've used it.
On another note, I would migrate from Access anyway - SQL 7 is much more
ndly to rapid application development than its predecessors, so you
might as well use the more powerful and faster SQL (or O e) server
(assuming you can afford the license, of course *grin*)
> -----Original Message-----
> From: Steve Muench [ HREF="mailto:smuench@us.oracle.com">mailto:smuench@us.oracle.com]
> Sent: 16 February 2000 06:43
> To: xsl-list@mu rytech.com
> Subject: Re: Which one to choose
>
>
> Ural,
>
> Portal sites typically strive for a perso zed
> experience. Personalization involves tracking lots
> of information about each user, their interests,
> their ferences, their screen layouts, etc.
> Serving personalized content involved querying
> your content repository to mat arious per-user
> preferences/interests against your smorgasbord
> of articles, stories, streaming video/audio, etc.
&
> Having all your content removed from a database
> and stored physically as XML files, you'll lose
> the lightnin st query times that enterprise
> relational databases can give the portal. The
> strategy most are going for is dynami y
> serving "slices" of data from (sometimes fairly
> hairy and finely-performance-tuned) SQL queries
> as dynamic content for XSLT-transforming
> it into:
>
> -> industry-standard DTD's for data exchange
> -> beautifu b pages
>
> Leading databases make this easy to do, to get
> the full performance, reliability, and
> maintain ity benefits of existing relational
> technology with the key benefits of XML.
>
> You might check out Oracle's fr XSQL Pages"
> technology and the accompanying XSQL Servlet that
> makes doing this *really* easy with your favorite
&g elational database (including ACCESS, if you use
> the JDBC/ODBC driver) and your favorite servlet
> engine -- not onl acle.
>
http://technet.oracle.com/tech/xml/xsql_servlet
______________________________________________________
Steve Muench, Lead XML Evangelist / Consulting Product Mgr
Oracle Cor usiness Components for Java Development Team
http://technet.oracle.com/tech/xm >
----- Original Message -----
From: "ural" <ural@ciol.com>
To: <xsl-list@mulberrytech.com>
Sent: Wednesday, Fe ry 16, 2000 2:59 AM
Subject: Which one to choose
| hi,,
| I am into a project where we have lot of content. In fact it is rtal
| site. a IT related news tutorials etc are there.
| So far we were using ASP and MS ACCESS for our contents. ie, we w
| storing all the file in our database. and depending on user request we are
| displaying to them. If we convert them into , then do you think it will
| be a good move or not. We have around 1500 articles in our site. I want to
| know wheter XML a right technology for large amount of content or not?
| If it is not then please suggest any other technology.
|
| rgds
| l
|
|
| XSL-List info and archive: http://www.mulberrytech.com/xsl/x ist
|
XSL-List info and archive: http://www.mulberrytech.com/xs l-list
XSL-List info and archive: http://www.mulberrytech.com/xs l-list