Hi,
I was looking at the implementation of feature counting by XSLT that
application schema uses and I'm wondering why the code is writing a
temporary file.
Given that the sources are anyways stream based, why go to the trouble
of writing a temp file, and not use the direct stream generated by the GML
encoder instead?
That would be me. I was not aware that xslt can be performed on a stream. Thanks for pointing that out
Victor Tey
Software Engineer
ASRDC
CSIRO Earth Science and Resource Engineering
Phone: +61 8 6436 8944
Victor.Tey@anonymised.com | www.csiro.au |
Address: Australian Resources Research Centre, 26 Dick Perry Avenue, Kensington WA 6151
PLEASE NOTE
The information contained in this email may be confidential or privileged. Any unauthorised use or disclosure is prohibited. If you have received this email in error, please delete it immediately and notify the sender by return email. Thank you. To the extent permitted by law, CSIRO does not represent, warrant and/or guarantee that the integrity of this communication has been maintained or that the communication is free of errors, virus, interception or interference.
Please consider the environment before printing this email.
-----Original Message-----
From: Andrea Aime [mailto:andrea.aime@anonymised.com]
Sent: Thursday, 25 October 2012 10:51 PM
To: Geoserver-devel
Subject: [Geoserver-devel] GML3 output schema XSLT writing to file
Hi,
I was looking at the implementation of feature counting by XSLT that application schema uses and I'm wondering why the code is writing a temporary file.
Given that the sources are anyways stream based, why go to the trouble of writing a temp file, and not use the direct stream generated by the GML encoder instead?
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Actually that is a bad excuse as I had obviously read the temp file in as stream and perform xslt on it. So I guess it would be I wasn't thinking then
Happy to make the fix
Cheers
-----Original Message-----
Hi Andrea,
That would be me. I was not aware that xslt can be performed on a stream. Thanks for pointing that out
Victor Tey
Please consider the environment before printing this email.
-----Original Message-----
From: Andrea Aime [mailto:andrea.aime@anonymised.com]
Sent: Thursday, 25 October 2012 10:51 PM
To: Geoserver-devel
Subject: [Geoserver-devel] GML3 output schema XSLT writing to file
Hi,
I was looking at the implementation of feature counting by XSLT that application schema uses and I'm wondering why the code is writing a temporary file.
Given that the sources are anyways stream based, why go to the trouble of writing a temp file, and not use the direct stream generated by the GML encoder instead?
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
