Comments below.
-----Original Message-----
From: Rajnish Pandey [mailto:Rajnish(_dot_)Pandey(_at_)sun(_dot_)com]
Sent: Friday, March 02, 2001 2:22 AM
To: ietf-openproxy(_at_)imc(_dot_)org
Subject: OMML
1.
<rule processing ...>
<property name="Cookie" matches="UserId=">
<action> proxylet://server/resource-path</action>
</property>
</rule>
In the above rule, action element specifies
proxylet://server/resource-path
Does "server" mean location of metadata from where the same
has to be downloaded
and then from the metadata , "location" element specifies
the location from
where proxylet has to be downloaded.
Is it like that ?
The "server" in the rule module is different from the "server" in
OMML. In the rule module it defined where the proxylet will run from,
e.g. 'localhost' or some other server. It's under the control of the
OPES box owner or whoever runs the OPES service, e.g. ISP, etc.
The "location" element specifies the location from where the
proxylet code needs to be downloaded from.
2.
In the "location" element , we can specify two locations for
the same proxylet.
In case one server is not responding , other one can be
always contacted for the
proxylet .Something like this ..
<location>b.com\proxylet.p1|a.com\proxylet.p1</location>
We could allow a list of locations to have the proxylet being
downloaded from, for very popular ones -:)
3.
In OMML draft , 2.2 ABNF grammar, it is written , "In most
cases localhost will
be used to specify the server as proxylets will run locally ."
Does it mean that, in this case there is no need of
downloading proxylet from
any other source and the proxylet is available locally along
with the metadata .
The proxylets are always downloaded to the Admin. server.
'localhost' means they run locally on the same host where the
rule base is matched. You can specify any server here.
Thanks
Christian