Re: [vwrap] one question

The very phrase protocol endpoint rather gives the answer. VWRAP describes
how to request things be done, and how data is delivered in response to
those requests. What the requester does with the data is out of scope,
There are descriptions about what the delivered data "means" but, that
merely means
that, just like a web page, if you request a page, parse it and then
generate subsequent requests based on a faulty or confused understanding of
the
delivered data your subsequent requests are likely to be poorly formed, and
generate error replied. Likewise if you request things of a VWRAP service
and build odd requests based on that, the VWRAP service will likely be
confused by those subsequent requests. (And being largely stateless REST
services will
happily say huh in the expected way)

- David
~ Zha

vwrap-bounces@ietf.org wrote on 09/22/2010 09:47:39 PM:

> From:
>
> Cristina Videira Lopes <lopes@ics.uci.edu>
>
> To:
>
> "vwrap@ietf.org" <vwrap@ietf.org>
>
> Date:
>
> 09/22/2010 09:48 PM
>
> Subject:
>
> [vwrap] one question
>
> Sent by:
>
> vwrap-bounces@ietf.org
>
> Let me summarize my main puzzlement with the drafts, and with some of
> the things stated here, with one very simple yes/no question that,
> hopefully, the group will get to a consensus in no time:
>
> I have a student starting to work on a JavaScript+HTML5 viewer for
> brain-dead-simple, multi-user, OpenSimulator-served scenes. I can do
> that very easily with OpenSim, since the client protocol is a plugin. Is
> VWRAP set up to develop protocols for interoperability between virtual
> worlds that, like these ones, use the web browser as the client?
> a) Yes
> b) No
>
> People's answers?
>
> _______________________________________________
> vwrap mailing list
> vwrap@ietf.org
> https://www.ietf.org/mailman/listinfo/vwrap