Re: [vwrap] Why are we standardizing the login handshake? (was RE: one question)

yes. clients request things from servers. user agents and renderers
are frequently clients. simulators can be clients in the sense that
the asset server serves requests from the client.

the way i look at it, "server push" is a type of response to a request
since the server waits for a client to be connected before pushing
assets.

so if you want to interpret server push to be outside the scope of
VWRAP, then i'm okay with not working on it, since no one here who's
going to implement anything VWRAPy is talking about doing it.

-cheers
-meadhbh
--
meadhbh hamrick * it's pronounced "maeve"
@OhMeadhbh * http://meadhbh.org/ * OhMeadhbh@gmail.com

On Fri, Sep 24, 2010 at 3:06 PM, Crista Lopes <lopes@ics.uci.edu> wrote:
> John,
>
> You may also want to read the intro draft.
> http://tools.ietf.org/html/draft-ietf-vwrap-intro-00
>
> This is in 4.4:
>
> "VWRAP defines formats  for describing objects and avatar shapes, but more
> importantly it
>   describes the mechanism by which those digital asset descriptions are
>   transferred between client applications, agent domains and region
>   domains."
> ...
> "Accessing and manipulating digital assets is  performed via capabilities
> which expose the state of the asset to an authorized client. "
>
> In other words, assets are fetched by the client. So if my world pushes them
> to the client, it's not VWRAP-compliant.
>
>
> _______________________________________________
> vwrap mailing list
> vwrap@ietf.org
> https://www.ietf.org/mailman/listinfo/vwrap
>