[Laszlo-dev] serverless operation
Oliver Steele
steele at laszlosystems.com
Wed Jan 19 14:45:31 PST 2005
On Jan 19, 2005, at 5:14 PM, Eric Bloch wrote:
> Some questions/comments:
>
> <snip>
>> Note that it is logically possible for /proxied instance/ to make
>> both proxied and unproxied requests. An /unproxied instance/ may only
>> make unproxied requests, because by definition there is no
>> server-side instance that could perform the proxying.
>
> I could see an odd case where you served up an instance via apache,
> but had it communicate to a running LZServlet proxy for certain
> runtime things.
> This doesn't seem critical. But it would change some of the things
> below wrt to what's possible and what's not. Or were you just trying
> to simplify here.
Right. We could also document the protocols that the runtime uses to
request server caching and acceptencodings, and that the LPS uses to to
encode back-end headers in a form that is accessible to the runtime,
but I would like to take these off the table for the initial
implementation.
>
>> DR4. [I had something here about acceptencodings and cacheable that I
>> don't have the heart to figure out again, but I think some of this
>> stuff becomes optional.]
>
> In 2.2, proxied requests may optionally have their back-end response
> encoded and available in the return dataset. Unproxied requests would
> not support this.
>
> Likewise, acceptencodings and cacheable attributes of the
> dataset/datasource would be ignored by unproxied requests. Perhaps it
> should be a compiler/runtime warning/error if you try to use these on
> an unproxied request.
>
>>
> _______________________________________________
> Laszlo-dev mailing list
> Laszlo-dev at openlaszlo.org
> http://www.openlaszlo.org/mailman/listinfo/laszlo-dev
More information about the Laszlo-dev
mailing list