[Laszlo-dev] An LPS server data proxy protocol for raw data, not just XML?

Wed Jul 30 15:13:29 PDT 2008

Raw proxying is useful, and might actually be good enough for all  
cases (incl. XML). Might even perform better. I do like the idea --  
although I also think developers need to get to the headers. Perhaps  
the client can separate out the headers.

However, for 4.2, I don't think JSON proxying is a requirement.  
Basically we're adding JSON at this point for the purposes of doing  
LPS->client data responses, which are generated by LPS. So I'd say  
defer this until post-4.2.

- D.

On Jul 29, 2008, at 1:52 PM, Henry Minsky wrote:

> The protocol we use for proxied data requests is  really only suitable
> for requesting
> well formed XML data. With the current protocol, the data comes back
> wrapped inside an XML document,
> which contains optional header data, and is assumed to be well  
> formed XML.
>
> e.g.,
> <resulset><body>DATA</body><headers>HEADERS</headers></resultset>
>
>
> As we want to support non XML protocols, like JSON, or raw text,
> which may need to be proxied
> through a server for security or other reasons, it would be nice to
> make the server proxy protocol
> support fetching arbitrary string content.
>
> My first thought is to add an extra flag to the request query args,
> which is something like "raw=true",
> and then the server would just proxy the request and send back the
> response verbatim. This
> would be simple, but would not allow any way to get the proxied
> response headers.
>
> I guess another idea would be to proxy the HTTP response verbatim,
> with the headers separated from the
> body by two blank lines. The client would need to parse as far as
> that, and could then take the rest of the
> response using substring(...).
>
> Any thoughts?  Am I looking for a solution without a problem?
>
>
>
>
> -- 
> Henry Minsky
> Software Architect
> hminsky at laszlosystems.com