Keep in mind that most (all?) JavaScript implementations out there
will choke if you try to store or manipulate 64-bit integers (signed
or unsigned), so for all JS code, you should treat ids as strings.
Of course, since ids are pretty much opaque values, this doesn't
really cause any problems; for example, it would never be meaningful
to add two user ids.
(Dan)
On Nov 8, 2007, at 12:10 PM, fernando padilla wrote:
>
> I haven't been paying attention, but I haven't heard something
> definitive about the id space.
>
> Anyhow. the Negative numbers might have something to do with unsigned
> long != two's complement signed long. So a 64bit id can be
> represented as an unsigned long (all positive numbers), or a two's
> complement signed long ( half of the bit space is negative ). I did
> bump into this earlier because they were giving out unsigned long ids,
> which java doesn't support, so we had to manually convert that
> unsigned long into a signed long.. hence we dealt with negative
> numbers.. :)
>
>
>
> On Nov 6, 2007 9:43 AM, Suhail Doshi <[EMAIL PROTECTED]> wrote:
>>
>> Sure I get an id like this: -7517143244711790000
>>
>>
>>
>> On Nov 6, 10:20 am, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
>> wrote:
>>> Hi, do you have any examples?
>>
>>
>>>
>>
>
> >
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"OpenSocial Developers" 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
-~----------~----~----~----~------~----~------~--~---
