[Opensim-dev] Suggested in-world DNS: .sim

[Cristina Videira Lopes]

You're making up your own definition of p2p in the context of opensim,  
your definition being "an opensim server and a viewer both running on  
the same box". That's not what p2p is, generally, although one could  
imagine a distribution that would have those as a unit. For "true" p2p  
VWs see OpenCobalt. OpenCobalt is both a server and a browser in the  
same piece of software, one doesn't exist without the other, it's not  
even modeled as server-and-client, it's a unit.

OpenSim is client-server. Even if a client and a server run on the  
same box, the architecture is still client-server. Your friend's  
viewer in his laptop needs to connect to your sim in your laptop in  
order to visit your world; at that point, it's up your opensim server  
to simulate your friend's agent and to serve all simulated data.  
That's where latency plays a role --home DSLs aren't good enough to  
support many clients sucking data from them. Also, your friend's  
opensim server in his latptop plays no role in the simulation of your  
friend's agent in your opensim server -- other than serving identity  
and inventory, in the case of HG, but not simulation.

So, again, not p2p as OpenCobalt. There's an interesting technical  
discussion waiting to happen comparing all these possible  
architectures. But let's start by not confusing things. OpenSim's  
architecture is completely different from OpenCobalt's.

On Feb 25, 2010, at 10:56 AM, Dzonatas Sol wrote:

> That doesn't answer my question.
>
> There are two opensim boxes, with each connected directly to each  
> other,
> peer to peer.
>
> Are you saying, of only these two boxes, that neither of them can a  
> client?
>
> I don't see the latency issue here when the client is directly on the
> opensim box.
>
>
> Melanie wrote:
>> I'm saying that one of them will run the sim. The other connects to
>> it. Even if the other also runs a sim, the sims will not be
>> connected. Much less cooperatively simulating.
>>
>> So, the one being connected to needs sufficient upstream bandwidth
>> as well as an externally identifiable name.
>>
>> Which means an ICANN-approved TLD. Not a fantasy TLD.
>>
>> Melanie
>>
>> Dzonatas Sol wrote:
>>
>>> If one opensim box connects to another opensim box, that is,
>>> technically, peer to peer.
>>>
>>> So, are you saying an opensim box cannot run a client at the same  
>>> time?
>>>
>>> Melanie wrote:
>>>
>>>> Hi,
>>>>
>>>> peer to peer simulation is not practical for many different  
>>>> reasons.
>>>> Latency being the chief one.
>>>>
>>>> OpenSim is not going to be a peer to peer system, therefore your
>>>> suggestion is off topic. Opensim doesn't need another TLD, and it  
>>>> is
>>>> not what you are envisioning. OpenSim firmly embraces the concept  
>>>> of
>>>> SERVER SIDE simulation, therefore every sim will always have a
>>>> central server.
>>>>
>>>> I believe this has gone as far as it will go and if there is any
>>>> more name calling, well, we'll just have to moderate some people,
>>>> won't we?
>>>>
>>>> Melanie
>>>> (Core)
>>>>
>>>>
>>>>
>>>>
>>> _______________________________________________
>>> Opensim-dev mailing list
>>> Opensim-dev at lists.berlios.de
>>> https://lists.berlios.de/mailman/listinfo/opensim-dev
>>>
>>>
>>>
>> _______________________________________________
>> Opensim-dev mailing list
>> Opensim-dev at lists.berlios.de
>> https://lists.berlios.de/mailman/listinfo/opensim-dev
>>
>>
>
> _______________________________________________
> Opensim-dev mailing list
> Opensim-dev at lists.berlios.de
> https://lists.berlios.de/mailman/listinfo/opensim-dev