Hi Michael,

 

Thank you for the quick response.

 

You make of course a valid point with (a) but there are of course situations in which you don’t control the environment and e.g. no java runtime environment is available.  But then again, I’m pretty sure most people would also agree that loading 40k lines of javascript code in the browser is less preferred then having native XSLT 2.0 support in the browser.

 

I know your company is already pushing boundaries of what it can achieve with the resources at hand. That’s why I was merely asking your opinion if it could be feasible with the generated stubs to do the transforms programmatically. 

 

I’m already pretty excited that we have a means to use XSLT 2.0 now without the need to setup some expensive framework on the server.

 

Kind regards,

Robby

 

 

 

From: Michael Kay [mailto:mike@saxonica.com]
Sent: Tuesday, September 20, 2011 1:09 AM
To: saxon-help@lists.sourceforge.net
Subject: Re: [saxon] question regarding Saxon-CE

 


I think there are several points to make:

(a) I haven't seen any explanation of why an application running server-side, written in JS, and needing access to an XSLT engine, would want to call an engine written in Javascript in preference to one written in Java. Presumably server-side Javascript is quite capable of invoking Java code. (This comment may simply betray my ignorance...)

(b) We're stretched enough for resources to deliver Saxon-CE on the browser; I don't think we can contemplate starting another project right now for a different environment. It wouldn't be the same product; the constraints and requirements are quite different. For example, a server side product would need to include a serializer, but the serializer has been stripped out from Saxon-CE as part of the effort to reduce the code size.

(c) There's clearly a need for a Javascript API to allow JS code to invoke the Saxon-CE transformation engine, but no such API exists yet. The focus has been on demonstrating the ability to produce an interactive user experience coded entirely in XSLT with no Javascript.

Michael Kay
Saxonica


On 19/09/2011 19:41, Robby Pelssers wrote:

Good evening,

 

I was reading upon usage of Saxon-CE at http://www.saxonica.com/ce/doc/coding/html-page.xml  The online documentation only shows the use case where you use it for transforming content from within the browser. But since server-side javascript  (e.g. NodeJS) has become a hot topic it would be really interesting to find out how to use the javascript XSLT processor on the server side instead of the client side.

 

I assume this is possible but the idea hasn’t been tested yet.    Can someone explain how one would use the stub to do a  transform programmatically on the server side?  So I am not requesting like in another thread to create a NodeJs module.  I’m simply asking for some API related hints on how to use the stub to get started.

 

Many thx in advance,

Robby Pelssers




------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1




_______________________________________________
saxon-help mailing list archived at http://saxon.markmail.org/
saxon-help@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/saxon-help