My first thought... specific interpretation, might be useful in some cases. Think about your query as a resource itself. - make the server support a resource - a query - PUT to create a query, giving it XML as representation, PUT returns id of the resource (you could name the quert I suppose) - you can now GET the query results - problem in this design is cleanup, you can have expiration on the query resource or delte after first GET or have explicit delete or have a cyclic buffer for the queries....
Not my an original idea:-) I think I got it from RESTful Web Services book.
