This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: Re: generating a repeatable unique id
- To: Sebastian Rahtz <sebastian dot rahtz at computing-services dot oxford dot ac dot uk>
- Subject: [xsl] Re: Re: generating a repeatable unique id
- From: Dimitre Novatchev <dnovatchev at yahoo dot com>
- Date: Mon, 30 Jul 2001 11:40:55 -0700 (PDT)
- Cc: xsl-list at lists dot mulberrytech dot com
- Reply-To: xsl-list at lists dot mulberrytech dot com
I don't see why you can't do exactly the same on the server.
Using IIS you could have the same Javascript code as part of an ASP page.
Cheers,
Dimitre Novatchev.
--- Sebastian Rahtz <sebastian.rahtz@computing-services.oxford.ac.uk> wrote:
> Dimitre Novatchev writes:
> > Both of this solutions are not too efficient.
> but portable!
>
> > There's a third one:
> >
> > Using DOM (I'm usng MSXML DOM), one can have the following Javascript code:
>
> Yes, but the point of my exercise is to get stuff server-side, not on
> the client (my users don't have an MSXML DOM to hand). If the problem
> was shifted to the client, I'd ship the whole document, and not get
> involved in later requests for a section.
>
> > So Sebastian, this is one of the most efficient ways (if in any
> > case you'll have to pass a parameter to the stylesheet) to
> > "dynamically" interprete an XPath expression, that will be known
> > only at "run time".
>
> I like the idea, and I agree, it would the right way to proceed
> client-side.
>
>
> Sebastian
>
__________________________________________________
Do You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messenger
http://phonecard.yahoo.com/
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list