I think this is logical and should be done at the level of the httpdataprovider. However, note that LPS proxying also includes media; we have no choke point to control media requests with data providers.

But -- please propose changes to public APIs before implementing them! We need to be deliberate about this. I learned yesterday that the visible/visibility API has been changed and that a new attribute or value (collapse?) had been added. I remember the thread, but had no recollection of this actually being done. Nobody understood why, including me. Of this more later...


On Aug 17, 2007, at 10:13 PM, Henry Minsky wrote:

yeah, that probably makes more sense in the case I was thinking about.

The use case I'm picturing is that someone wants to run an app which
needs data proxy service (because of security restrictions in the swf
or DHTML environment), and they don't want to be running an piggish
Java servlet engine and LPS server. They may be serving the app from
an apache/PHP server, for example, and have a PHP script which acts as
a data proxy.


In this case, it would be simplest for the user to configure the
default httpdataprovider with the proxy script url in one place, at
the initialization of their app, before any data requests are made. So
having an API call on the httpdataprovider would make more sense than
setting it on each dataset.




On 8/18/07, David Temkin <[EMAIL PROTECTED]> wrote:
should proxying be considered a policy that is implemented by a
dataprovider?


On Aug 17, 2007, at 8:33 PM, Henry Minsky wrote:

Change 20070817-hqm-4 by [EMAIL PROTECTED] on 2007-08-17 22:42:46
EDT
    in /cygdrive/c/users/hqm/openlaszlo/wafflecone2
    for http://svn.openlaszlo.org/openlaszlo/branches/wafflecone

Summary: add option to set proxy host url for proxied HTTP data
requests

New Features: add option to set proxy host url for proxied HTTP
data requests

Bugs Fixed: LPP-4449

Technical Reviewer: pkang  (pending)
QA Reviewer: max (pending)
Doc Reviewer: (pending)

Documentation:

Release Notes:

Details:

new API call to LzDataset, setProxyURL, allows you to specify an
explicit proxy
host server to use for proxied data requests.

proxyurl can also be set as a dataset attribute



Tests:

test/lfc/data/proxydata.lzx


Files:
M      test/hello.lzx
M      WEB-INF/lps/lfc/kernel/swf/LzHTTPLoader.as
M      WEB-INF/lps/lfc/kernel/dhtml/LzHTTPLoader.js
M      WEB-INF/lps/lfc/data/LzDataRequest.lzs
M      WEB-INF/lps/lfc/data/LzHTTPDataProvider.lzs
M      WEB-INF/lps/lfc/data/LzDataset.lzs
A      test/lfc/data/testproxyhost.lzx

Changeset: http://svn.openlaszlo.org/openlaszlo/patches/20070817-
hqm-4.tar


--
Henry Minsky
Software Architect
[EMAIL PROTECTED]




--
Henry Minsky
Software Architect
[EMAIL PROTECTED]

Reply via email to