I'm investigating on behalf of the XMLNuke project a good way to accomplish this.
The question is if there's any way to declare an alternative server-side response in case XSLT processing is not available (or possibly if it takes to long time) in the client Browser?
This would be important so to let it fall back to server-side XSLT processing to have compability to older versions or other brands of browsers.
I realize it might be out of the scope of Clean AJAX purpous, but maybe you could suggest any soloution based on clean AJAX to accomplish this.
Any response will be highly regarded.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Henrik, your question is very interesting.
This fallback behavior could be reached today, unfortunally not at high level, because the XSLT implementations available.
One possible solution is to perform a request using XSLT, if you capture any XSLT exception on this request then a 2nd request, to a resource that does not require XSLT, could be performed.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The Freja javascript engine claims to do it this way (however doesn't fill all other requirements as good as Clean). I think I'll look into the Freja code base to get some idea how to implement this particular behaviour.
Else I go with some other method of pretesting and directing with some kind of front-side (client-side javascript) controller, which would cover the 2 first levels on the 4 level design.
If you're interested I can share with you when I've got something working.
Anyways, your response is most appriciated. Keep up the good work :-)
Maybe I've missed it while looking over the info on Clean-Ajax at it's website, and if that's the case I apologies.
My question is based on my concept of "4 level XHTML XSL Transformation" as described here:
http://sourceforge.net/tracker/index.php?func=detail&aid=1502683&group_id=52740&atid=467872
I'm investigating on behalf of the XMLNuke project a good way to accomplish this.
The question is if there's any way to declare an alternative server-side response in case XSLT processing is not available (or possibly if it takes to long time) in the client Browser?
This would be important so to let it fall back to server-side XSLT processing to have compability to older versions or other brands of browsers.
I realize it might be out of the scope of Clean AJAX purpous, but maybe you could suggest any soloution based on clean AJAX to accomplish this.
Any response will be highly regarded.
Henrik, your question is very interesting.
This fallback behavior could be reached today, unfortunally not at high level, because the XSLT implementations available.
One possible solution is to perform a request using XSLT, if you capture any XSLT exception on this request then a 2nd request, to a resource that does not require XSLT, could be performed.
OK, thanx for your prompt response.
The Freja javascript engine claims to do it this way (however doesn't fill all other requirements as good as Clean). I think I'll look into the Freja code base to get some idea how to implement this particular behaviour.
Else I go with some other method of pretesting and directing with some kind of front-side (client-side javascript) controller, which would cover the 2 first levels on the 4 level design.
If you're interested I can share with you when I've got something working.
Anyways, your response is most appriciated. Keep up the good work :-)
BTW Freja is found at:
http://www.csscripting.com/wiki/index.php?title=Freja
I thank you for your interest on the project, and it will be a pleasure to share experiences.
Regards.