Saxon » Saxon-CE

I think there are two parts to this: (a) making the request asynchronous, and (b) providing more control than you get via the doc() function.

Do you need more from GET requests than doc() gives you (other than asynchroneity)?

Or are you mainly concerned with doing other kinds of request, e.g. PUT?

I don't think it would be too difficult to do something like

which does an asynchronous request to fetch an XML document from a given URI and then fires a transformation to process it in the given mode as soon as it arrives.

But I don't know how much of the requirement that would meet.

We need to be very conservative about adding extensions to CE, since we don't want to bloat the code size: we should aim to get it down further rather than increasing it.

Michael Kay Saxonica

fn:doc being sync is a bit of an issue, but I am more concerned about scenario b).

Wanting to perform async HTTP GET/POST/PUT/DELETE from saxon-ce 'out of the box' is #lazyweb on my part.

I guess the answer could be an external (EXPATH ?) function library instead of a built in but I don't have the time to write yet another func library, but that being said I will end up writing something in javascript to get the basic REST functionality I need.

J

Let us know how you get on and we'll see what we can do to productize it.

(One of the reasons I've never incorporated an HTTP library in the main Saxon product is the difficulty of doing automated tests. We need to tackle that.)