paul, my current thoughts are along those lines.
what exactly will opensocial.getEnvironment().getDomain() produce, for
a Hi5 for example? Hi5.com? or will it vary
jdavidnet.sandbox.hi5.com
jdavidnet.hi5.com
profiles.hi5.com
etc...
what happens if getDomain() changes over time and produces a different
result. predicting the userid might break unexpectedly over time.
if i do socialhelix.createUser(userid) via a web service call made
through makeRequest i should have the referrer url which might be more
durable over time than getDomain(), but i do not know.
i think what it comes down to, is that i always need someone to have a
socialhelix userid, and from each of the social networks, there will
be pointers or GUIDEs to my userids.
right now i am thinking the userid or rather GUIDE (Globally Unique
IDEntification) will be 2 parts, but more folder like so
definition GUIDE = {tld}\{userid}
users.socialhelix.net\userid\hi5.com\{uid}
users.socialhelix.net\userid\orkut.com\{uid}
users.socialhelix.net\userid\myspace.com\{uid}
users.socialhelix.net\userid\socialhelix.net\{uid}
this results in a definition that is filesystem and url safe.
and then if i want to file system optimize i might split the IDs every
so many chars for good static branching, but that does not need to be
part of the link standard. Jason seemed to think that 32k files/dirs
per listing were a reasonable limit. our user ids will be 32bit char
encoded, so that they are linux and windows file system safe. with
jason's advice from the hackathon that would mean putting in slashes
every 3-4 chars depending on expected fill density.
thoughts?
On Mar 3, 7:29 pm, Paul Lindner <[EMAIL PROTECTED]> wrote:
> How about creating your unique IDs with
>
> opensocial.getEnvironment().getDomain() + ID
>
>
>
> On Mon, Mar 03, 2008 at 05:08:22PM -0800, jdavid.net wrote:
>
> > is there a defined standard/ registration to guarantee a unique id
> > given a user on a social network.
>
> > we are looking at providing a widget that will need to store data for
> > the user beyond the user persistence data cache, and we will need a
> > globally unique idea between all users on all networks.
>
> > i read somewhere that google recommended userid(s) that look like
> > {userid} is [A-Za-z0-9]
>
> > hi5:{userid}
> > myspace:{userid}
> > ning:{userid}
> > orkut:{userid}
>
> > in theory this is grand, but if we are addressing things based on
> > REST, then
>
> > : becomes %3A in the url or
>
> > hi5%3A{userid}
>
> > which does not seem as clean
>
> > if we used +,_,-,. we might have a cleaner global id
>
> >http://externalprovider.com/userid/hi5+{userid}
> >http://externalprovider.com/userid/hi5.{userid}
> >http://externalprovider.com/userid/hi5-{userid}
> >http://externalprovider.com/userid/hi5_{userid}
>
> > what does everyone else think?
> > it would be nice if openSocial just returned the global id, rather
> > than a local one, so that widgets and sdks are not adding them.
> > You received this message because you are subscribed to the Google Groups
> > "OpenSocial Application Development" group.
> > To post to this group, send email to opensocial-api@googlegroups.com
> > To unsubscribe from this group, send email to [EMAIL PROTECTED]
> > For more options, visit this group
> > athttp://groups.google.com/group/opensocial-api?hl=en
> > -~----------~----~----~----~------~----~------~--~---
>
> --
> Paul Lindner
> hi5 Architect
> [EMAIL PROTECTED]
>
> application_pgp-signature_part
> 1KDownload
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"OpenSocial Application Development" group.
To post to this group, send email to opensocial-api@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/opensocial-api?hl=en
-~----------~----~----~----~------~----~------~--~---
