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

[Meadhbh Hamrick <[e-mail]>]

yup. the terms "client" and "server" frequently get confused.

i've already suggested we use the terms "user agent" and "renderer" to
be more precise in our usage concerning what kinds of messages they
generate or consume.

another way we've used the terms relate to who initiates connections.
"servers" are things that sit behind routable internet addresses.
"clients" may live behind NATted firewalls and are the ones that
initiate connections.


--
meadhbh hamrick * it's pronounced "maeve"
@OhMeadhbh * http://meadhbh.org/ * [e-mail]



On Fri, Sep 24, 2010 at 3:16 PM, Crista Lopes <[e-mail]> wrote:
> On 9/24/2010 3:11 PM, Hurliman, John wrote:
>>>
>>> -----Original Message-----
>>> From: [e-mail] [mailto:[e-mail]] On Behalf
>>> Of Crista Lopes
>>> Sent: Friday, September 24, 2010 3:07 PM
>>> To: [e-mail]
>>> Subject: Re: [vwrap] Why are we standardizing the login handshake? (was
>>> RE: one question)
>>>
>>> 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.
>>>
>>>
>>
>> You keep saying "if my world does X, it's not VWRAP-compliant". That's not
>> correct. "If my world does not have service endpoint X, it's not
>> VWRAP-compliant" is the correct statement here. Your world can send assets
>> to your client in any way it wishes, but if your asset service does not
>> expose a VWRAP asset fetch capability (regardless of whether your own client
>> uses it or not) then it is not VWRAP-compliant.
>>
>
> So what exactly does this mean? (especially the 2nd sentence, the 1st is
> just for context of the word "client")
>
>> "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. "
>
>
> _______________________________________________
> vwrap mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/vwrap
>