Re: [mmox] OGP scalability concerns

[Christian Scholz <[e-mail]>]

Hurliman, John schrieb:
>> we also use the term "domain" in it's more traditional sense to
>> imply a bounds of authority. which is to say, we assume that all
>> hosts and services inside a domain are administered by the same
>> entity. that being said, there's no reason you can't have
>> sub-domains, and there's no reason that two services associated
>> with "the" agent domain can't be split across two administrative
>> domains (like maybe yahoo or AOL get in the business of moving
>> virtual world IM messages but don't want to deploy a world
>> themselves.) it would require some coordination of identity
>> management issues, but i'm sure they're tractable.
> 
> I understand this. If you are Linden Lab and you are already in the
> business of running lots of independent services (content hosting,
> identity storage and authorization, instant messaging, inventory
> servers, simulators, etc) then it makes sense to lump every service
> you want to provide under one trust domain. Simulation can be a
> different domain so third party simulators like OpenSim can run under
> a separate trust domain and optionally connect to the aggregate
> Linden Lab service cloud. Tada! You have OGP. It's a great business
> model. Unless you are any company *except* Linden Lab and you want to
> provide a service such as content hosting without becoming a full
> virtual world service provider.

It also reminds me of Facebook and Facebook connect where you also only 
get all or nothing. Moreover FB also defines who actually has access to 
_your_ data (e.g. Google has not). Nevertheless other players such as 
MySpace or Yahoo (and others) are becoming more open in a per-service 
level, e.g. providing OAuth based access to profile or friends data.

What's missing there is still some way to list all of your services 
together and to find out which services a site provides. But there is 
work going on to solve these problems. I guess a good resource is Eran's 
blog (which I also should monitor more closely as a lot has happened 
there since I last looked, namely thoughts about delegated authorization 
as we might need it and XRD vs. XRDS):

http://www.hueniverse.com

> Using the current evolution of the web as historical evidence and
> assuming that specialized service providers will be the norm, lumping
> together instant messaging and content hosting under the same
> umbrella doesn't make any sense. This is why I'm in favor of starting
> from the ground up and defining each use case and service endpoint,
> rather than trying to figure out clever ways of shoehorning the
> "right" approach into Linden Lab's OGP.

+1

-- Christian


-- 
COM.lounge GmbH
http://comlounge.net
Hanbrucher Strasse 33, 52064 Aachen
Amtsgericht Aachen HRB 15170
Geschäftsführer: Dr. Ben Scheffler, Christian Scholz

email: [e-mail]
fon: [phone]
fax: [phone]

personal email: [e-mail]
personal blog: http://mrtopf.de/blog
personal podcasts: http://openweb-podcast.de, http://datawithoutborders.net