Re: [ogpx] Teleports and protocol resilience

:) I fell in that trap many times.
But what about the the entity to serialise the avatar data to at derez? You
mentioned either agent domain or destination region.
the tp draft uses the region, with as a consequence a second pass trough the
source region.
What are the argument pro and contra this solution compared to serialising
to the AD?
I have the feeling the slightly non-obvious path in the draft was picked for
a good reason, but i do not know enough about the details to see why.

-Vaughn

On Tue, Oct 13, 2009 at 8:12 PM, Joshua Bell <josh@lindenlab.com> wrote:

>
> On Tue, Oct 13, 2009 at 10:31 AM, Vaughn Deluca <vaughn.deluca@gmail.com>wrote;wrote:
>
>> @Joshua
>> RD is not the same as Region, in the TP drafs its the Region(service) that
>> has the interface.
>>
>>
> Oops - you're right, of course. Everything we're talking about on this
> thread can occur within a single RD or between two RDs. I was sloppily using
> "RD" as shorthand for "collection of services that implement region
> behavior" but in this case we need to be more precise.
>
> _______________________________________________
> ogpx mailing list
> ogpx@ietf.org
> https://www.ietf.org/mailman/listinfo/ogpx
>
>