[vwrap] End point "behavior" (was: one question)

[Boroondas Gupte <[e-mail]>]

 I'm not up to date with everything here, so I hope I don't get it
completely wrong, but here's my take:

On 09/23/2010 05:20 PM, Cristina Videira Lopes wrote:
> In other words, if my viewer is in JavaScript, I have to make the
> JavaScript program do things in specific ways, and not others, in
> order to be able to interoperate in VWRAP?
Only regarding what they /send/ and /receive/ over the wire when
communicating with VWRAP services, I think. The web analog would be that
to talk to a web server, you have to speak and understand HTTP.
Depending on what server it is and what you'd like to do with it, there
might be additional requirements, e.g. WebDAV (just an arbitrary example
out of many). What you do within the bounds of these protocols and what
other processing you do (including interfacing non-HTTP resources) is
completely up to you.

Likewise, to talk to a VRAP service, you'll have to speak and understand
VWRAP.core and, depending on the kind of service and what you want from
it, the relevant VWRAP.<insert service type here> protocols. What you do
within the bounds of these protocols and what other processing you do
(maybe interfacing non-VWRAP resources) is again up to you.

So the "behavior" of the end point only matters in a black-box way: in
what can be seen from the VWRAP services. Whatever happens inside (or at
the non-VWRAP sides of the box) is out-of-scope for a communication
protocol.

Cheers,
Boroondas