[Pyogp] Agent domain

[Locklainn]

Tao,
You had a question about how to contact region domain:

request_avatar_url:

region_url + '/agent/' + agent_id + 'rez_avatar'

[Christian Scholz]

Post by Locklainn
Tao,
region_url + '/agent/' + agent_id + 'rez_avatar'

Thanks!

Nevertheless I cannot connect to e.g. sim1 port 13000.

(and interestingly enough the agent domain login now gives me a 404 so
not even the existing login script seems to work anymore. I don't think
I changed something on my side but as it's late I am not completely sure
of course ;-)

-- Christian

[Tess Chu]

This works as expected. Those ports on the Second Life simulators are
currently only internal ports and in order to publicly expose these web
services, we would have to wrap caps around it, and make that part of
the protocol. We did a whiteboard discussion of how agent domain
-region domain trust is established, but have not yet done the design or
begin the implementation on that yet.

On the OpenSim side, Zha specifically had his servers whitelist the
Linden Lab IP range so that we can directly invoke that URL on his
regions. This is a workaround to the trust-establishment piece. We
weren't too rushed to do the trust establishment piece yet since we've
been working with this workaround.

The next steps on our list are mainly to get 1. Beta stability for July
31st and 2. Get design docs written and protocols written to follow the
design so that we can test against the right things.

Tess

Post by Christian Scholz

Post by Locklainn
Tao,
region_url + '/agent/' + agent_id + 'rez_avatar'

Thanks!
Nevertheless I cannot connect to e.g. sim1 port 13000.
(and interestingly enough the agent domain login now gives me a 404 so
not even the existing login script seems to work anymore. I don't
think I changed something on my side but as it's late I am not
completely sure of course ;-)
-- Christian

[Christian Scholz]

Hi1

Post by Tess Chu
This works as expected. Those ports on the Second Life simulators are
currently only internal ports and in order to publicly expose these web
services, we would have to wrap caps around it, and make that part of
the protocol. We did a whiteboard discussion of how agent domain
-region domain trust is established, but have not yet done the design or
begin the implementation on that yet.

Ah ok, I thought that might not matter on the test grid ;-)
But it stops me unfortunately from finishing my agent domain
implementation. What I might do now is to get OpenSim with Zha's patch
and try to do this locally.

As I saw from the OpenSim code, is it only rez_avatar what is used and
not request_rez_avatar?

Thanks for the explanation!

-- Christian

[Ann Otoole]

Where is the Intellectual Property Rights control in all this?
Nice work getting the code in place but seems like you are missing a major chunk here.



----- Original Message ----
From: Tess Chu <***@lindenlab.com>
To: Christian Scholz <***@comlounge.net>
Cc: ***@lists.secondlife.com
Sent: Monday, July 14, 2008 1:21:13 PM
Subject: Re: [Pyogp] Re: Agent domain

This works as expected. Those ports on the Second Life simulators are
currently only internal ports and in order to publicly expose these web
services, we would have to wrap caps around it, and make that part of
the protocol. We did a whiteboard discussion of how agent domain
-region domain trust is established, but have not yet done the design or
begin the implementation on that yet.

On the OpenSim side, Zha specifically had his servers whitelist the
Linden Lab IP range so that we can directly invoke that URL on his
regions. This is a workaround to the trust-establishment piece. We
weren't too rushed to do the trust establishment piece yet since we've
been working with this workaround.

The next steps on our list are mainly to get 1. Beta stability for July
31st and 2. Get design docs written and protocols written to follow the
design so that we can test against the right things.

Tess

Post by Christian Scholz

Post by Locklainn
Tao,
region_url + '/agent/' + agent_id + 'rez_avatar'

Thanks!
Nevertheless I cannot connect to e.g. sim1 port 13000.
(and interestingly enough the agent domain login now gives me a 404 so
not even the existing login script seems to work anymore. I don't
think I changed something on my side but as it's late I am not
completely sure of course ;-)
-- Christian

_______________________________________________
Click here to unsubscribe or manage your list subscription:
https://lists.secondlife.com/cgi-bin/mailman/listinfo/pyogp




-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.secondlife.com/pipermail/pyogp/attachments/20080714/a35046c3/attachment-0001.htm

[Christian Scholz]

Post by Ann Otoole
Where is the Intellectual Property Rights control in all this?
Nice work getting the code in place but seems like you are missing a major chunk here.

What we do here is nothing which will get deployed. It is mostly for
playing around with concepts. As Tess pointed out, the trust issue will
be handled (long before it goes public).
What I am talking about is really just a private grid of one region and
one agent domain running on my own machine which has no connection to
the outside world (because the outside world right now has big walls
around it so it's not even possible to connect to any live region like
that). In fact I expect to be rather naked in it.

I would like to learn more about that whiteboard discussion Tess
mentioned though :-)

Hope that helps,

Christian

Post by Ann Otoole
----- Original Message ----
Sent: Monday, July 14, 2008 1:21:13 PM
Subject: Re: [Pyogp] Re: Agent domain
This works as expected. Those ports on the Second Life simulators are
currently only internal ports and in order to publicly expose these web
services, we would have to wrap caps around it, and make that part of
the protocol. We did a whiteboard discussion of how agent domain
-region domain trust is established, but have not yet done the design or
begin the implementation on that yet.
On the OpenSim side, Zha specifically had his servers whitelist the
Linden Lab IP range so that we can directly invoke that URL on his
regions. This is a workaround to the trust-establishment piece. We
weren't too rushed to do the trust establishment piece yet since we've
been working with this workaround.
The next steps on our list are mainly to get 1. Beta stability for July
31st and 2. Get design docs written and protocols written to follow the
design so that we can test against the right things.
Tess

Post by Christian Scholz

Post by Locklainn
Tao,
region_url + '/agent/' + agent_id + 'rez_avatar'

Thanks!
Nevertheless I cannot connect to e.g. sim1 port 13000.
(and interestingly enough the agent domain login now gives me a 404 so
not even the existing login script seems to work anymore. I don't
think I changed something on my side but as it's late I am not
completely sure of course ;-)
-- Christian

_______________________________________________
https://lists.secondlife.com/cgi-bin/mailman/listinfo/pyogp
------------------------------------------------------------------------
_______________________________________________
https://lists.secondlife.com/cgi-bin/mailman/listinfo/pyogp

[Tess Chu]

Just to be clear, Intellectual Property Rights are not being violated
here because we are not sending assets across. You can connect any
OpenSim region, but when you login or teleport there, no assets are
actually sent. That's why you end up Ruth'ed and without any inventory.

Tess

Post by Christian Scholz

Post by Ann Otoole
Where is the Intellectual Property Rights control in all this?
Nice work getting the code in place but seems like you are missing a major chunk here.

What we do here is nothing which will get deployed. It is mostly for
playing around with concepts. As Tess pointed out, the trust issue
will be handled (long before it goes public).
What I am talking about is really just a private grid of one region
and one agent domain running on my own machine which has no connection
to the outside world (because the outside world right now has big
walls around it so it's not even possible to connect to any live
region like that). In fact I expect to be rather naked in it.
I would like to learn more about that whiteboard discussion Tess
mentioned though :-)
Hope that helps,
Christian

Post by Ann Otoole
----- Original Message ----
Sent: Monday, July 14, 2008 1:21:13 PM
Subject: Re: [Pyogp] Re: Agent domain
This works as expected. Those ports on the Second Life simulators are
currently only internal ports and in order to publicly expose these web
services, we would have to wrap caps around it, and make that part of
the protocol. We did a whiteboard discussion of how agent domain
-region domain trust is established, but have not yet done the design or
begin the implementation on that yet.
On the OpenSim side, Zha specifically had his servers whitelist the
Linden Lab IP range so that we can directly invoke that URL on his
regions. This is a workaround to the trust-establishment piece. We
weren't too rushed to do the trust establishment piece yet since we've
been working with this workaround.
The next steps on our list are mainly to get 1. Beta stability for July
31st and 2. Get design docs written and protocols written to follow the
design so that we can test against the right things.
Tess

Post by Christian Scholz

Post by Locklainn
Tao,
region_url + '/agent/' + agent_id + 'rez_avatar'

Thanks!
Nevertheless I cannot connect to e.g. sim1 port 13000.
(and interestingly enough the agent domain login now gives me a 404
so not even the existing login script seems to work anymore. I don't
think I changed something on my side but as it's late I am not
completely sure of course ;-)
-- Christian

_______________________________________________
https://lists.secondlife.com/cgi-bin/mailman/listinfo/pyogp
------------------------------------------------------------------------
_______________________________________________
https://lists.secondlife.com/cgi-bin/mailman/listinfo/pyogp