Hello Jason, yes it does (I realized it was rather a stupid question
as well :) )
On Oct 6, 11:51 pm, Jason <[EMAIL PROTECTED]> wrote:
> Hi Kogan. You can store the items in theback-endand associate them
> with the user's ID. When a user tries to add an item, use a
> makeRequest call to send a
Hi Kogan. You can store the items in the back-end and associate them
with the user's ID. When a user tries to add an item, use a
makeRequest call to send a signed HTTP request to your back-end with
the item information. The ID of the user will be sent as a parameter
with the signed request so you
Hello Jason,
my use case is this -
I want to save:
(*on my back end server, not using the persistence API or something
like that, that allows me a small memory space to use using Orkut
itself)
a list of lets say "items" for each user that has my application. That
is, my application lets a user ad
Hi Kogan. In general, you shouldn't need to recreate the social graph
in your database. Is there a reason why you can't just query orkut for
the list of friends every time a user tries to use your application?
What is your use case, exactly? orkut is not going to trigger an "add
friend" event that
4 matches
Mail list logo
