RE: Complex XSL Application (I think)

["Vun Kannon, David" <dvunkannon@xxxxxxxx>]

	You posit two uses of XSL, during query and response. I assume you
are querying 160k records in a database, not an XML file of 1.6MB++. The use
of XSL on the response is pretty obvious - something chunks up the database
response as XML encoded objects, those objects get styled into HTML on the
server side (safer today than figuring out if the client UA can work with
the XML+XSL).
	You could use XSL on the inbound query if the query were also
encoded in XML, the stylesheet would transform the query into a SQL
statement. The only problem here is that the HTML form values are not going
to show up at your front door as XML, rather as a list of tag-value pairs.
These will have to be reworked back into structured objects before you can
hand off to the transform.
Cheers,
David vun Kannon
Manager, KPMG LLP
Financial Services Consulting

> -----Original Message-----
> From:	Wendy Cameron [SMTP:wendy.cameron@xxxxxxxxx]
> Sent:	Tuesday, February 23, 1999 8:26 PM
> To:	xsl-list@xxxxxxxxxxxxxxxx
> Subject:	Complex XSL Application (I think)
> 
> Well we are trying to archive 160,000 employee records from an
> decommisioned
> human resources system. (Each record aproximately 10k therefore total
> archive is around 1.6Meg).  This is Proof of Concept Trial in which we are
> trying to prove the capabilities of XML and XSL.  There fore we would like
> to as much as possible avoid the use of JavaScript and non XML XSL
> technologies.
> 
> We are trying to provide very simplistic querying on the data.
> 1) Find an employee by Service Number
> 2) Find an employee by name segment
>      eg I search for all records with Wendy in the name field
>      Where the name field contains the whole name.
> 
> I have been experimenting with XML and XSL under IE5 and have made
> progress.
> 
> However my next hurdle is
> 
> Using server side XSL and connecting that server side XSL up with client
> side XSL.  I am just trying to get number 1) working.
> 
> Mark Birbeck wrote:
> 2. If you have server-side scripting then another method would be to
> generate the XSL dynamically - the browser won't know any different.
> 
> This sounds related to what im trying to do.
> You can assume I have server side scripting
> Could anyone expand on this and explain how i might acheive the following
> 
> I need to get the Service Number from the user (Browser)
> Pass this value to the server
> Create the XSL to produce an XML file with just that employees information
> Pass this new XML file to the browser XSL for rendering in the browser.
> 
> BTW: Im fairly new to XSL and XML and the DOM
> So any examples of particular features I may need to use would be greatly
> appreciated.
> 
> Regards Wendy
> 
> 
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
*****************************************************************************
The information in this email is confidential and may be legally privileged.
It is intended solely for the addressee. Access to this email by anyone else
is unauthorized. 

If you are not the intended recipient, any disclosure, copying, distribution
or any action taken or omitted to be taken in reliance on it, is prohibited
and may be unlawful. When addressed to our clients any opinions or advice
contained in this email are subject to the terms and conditions expressed in
the governing KPMG client engagement letter.         
*****************************************************************************


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list