Limits for REST/RPC API

[Badaro]

--- Situation

I just found out through the forum that HttpRequest will be removed
from OS Templates, and we'll be forced to migrate all profile data to
the user AppData. The related thread is here:
http://groups.google.com/group/opensocial-orkut/browse_thread/thread/f6dd9304ff16aff6#

However, I have an application with several hundred thousand users,
where part of the data needed for the profile is stored in my servers.
Therefore, I'll need to implement an automated procedure to migrate
this data to Orkut, and I believe my only reasonable option is to use
the REST/RPC API to upload this data.

-- Question

Is there a limit to the number of requests that can be made for one
application? More specifically, I'm talking about the
OpenSocialClient.newUpdatePersonAppDataRequest call.

[Shishir Birmiwal (Google)]

Yes, there is a limit to the number of updatePersonAppDataRequests
that can be made per app per person, but given that you're going to
update for each person, you will not hit the limit.

Cheers,
Shishir

On May 18, 7:00 pm, Badaro <bad...@gmail.com> wrote:
> --- Situation
>
> I just found out through the forum that HttpRequest will be removed
> from OS Templates, and we'll be forced to migrate all profile data to

> the user AppData. The related thread is here:http://groups.google.com/group/opensocial-orkut/browse_thread/thread/...

[Badaro]

Can you tell us how much is that limit, and what happens when we hit
it?

While this limit doesn't affect this migration process, after we
migrate the profile information to AppData we will need to update it
constantly to keep the user profile up-to-date.

Filipe Badaro

On May 19, 6:00 am, "Shishir Birmiwal (Google)"

[Apurv Gupta]

Hi Filipe,

What's your use case for updating the AppData? What's your application url?

Thanks,

-apurv

[Apurv Gupta]

If you can tell us more, we can help you better. It may be entirely true that your app is better off using a different rendering model.

[Badaro]

This is the development version of the profile, which is currently
using OS Templates with HttpRequest:
http://sandbox.orkut.com/Main#AppInfo.aspx?appUrl=http%3A%2F%2Fbadaro.labone.net%2Fsonoraorkut%2Fsonorasocialv01.aspx

The live application is here:
http://www.orkut.com.br/Main#AppInfo.aspx?appId=1086790722195

We have not yet uploaded the OS Templates with HttpRequest version of
the profile to production, since we're still deciding if we should do
this right now, or wait until we modify the application to use
AppData.

The profile intends to give the viewer a sample of the owner's musical
tastes, including some of his favorite artists and musics. It used to
include a lot of extra functionality, such as allowing the viewer to
preview and rate the songs displayed, but sadly this can't be done
with the more restricted environment of OS Templates.

Currently, since we're using HttpRequest, we send a random set of the
owner's favorites on each visit, but after we change to AppData this
would no longer be possible, so we'd probably include either the most
recent changes, or the highest ranked ones.

However, this data is bound to change often, in particular for new
users, since they have no data to begin with. It's certain that for
the first few uses of the application we'd be updating the AppData
constantly as we get more information about the user's tastes.

That being said, I *don't* want to use AppData for this, however if
HttpRequest is removed I believe I won't have any other choice to
store the profile data.

Filipe Badaro

On May 19, 12:20 pm, Apurv Gupta <apurv.gu...@gmail.com> wrote:
> If you can tell us more, we can help you better. It may be entirely true
> that your app is better off using a different rendering model.
>

[Badaro]

To save you some time, here's my profile in the Sandbox:
http://sandbox.orkut.com.br/Main#Profile.aspx?uid=13771854167387711188

It should give you an idea on what the profile looks like with the
data already in place.

Filipe Badaro

On May 19, 2:21 pm, Badaro <bad...@gmail.com> wrote:
> This is the development version of the profile, which is currently

> using OS Templates with HttpRequest:http://sandbox.orkut.com/Main#AppInfo.aspx?appUrl=http%3A%2F%2Fbadaro...

[Badaro]

A couple more things that probably weren't very clear from my
explanation:

- What defines *when* the data in the profile should be updated are
the user's interactions with the application in the canvas. As he adds/
rates more songs and artists and changes what his favorites are, the
profile should be updated to reflect this.

- We probably will be using the JS API instead of REST/RPC for those
updates, though I imagine the limits are the same.

Filipe Badaro

On May 19, 2:21 pm, Badaro <bad...@gmail.com> wrote:

> This is the development version of the profile, which is currently

> using OS Templates with HttpRequest:http://sandbox.orkut.com/Main#AppInfo.aspx?appUrl=http%3A%2F%2Fbadaro...

[Apurv Gupta]

You don't need to worry about it then. As long as you are doing this in response to user action, you should be fine.

I was worried about a news-like scenario, where you try to update the app data for all users in background as stories appear.

Watch out for 10KB limit of storage on per user per app. Some apps keep only the recent/important information in appData and rest on their servers [if needed].

[gcb]

what about feed readers?

What if my 1mi users want fresh items everytime someone reads his
profile?

say I have an app that shows his twits.

[Eduardo Rocha]

IMHO, the users should go to canvas view for that.

The scenario I see with profile changes (and we probably must face it)
is that there is less room for application features on profile view,
which actually can be a good thing, because we can choose simpler
solutions and have less work :)

[Apurv Gupta]

+1 to eduardo. Profile view is meant to showcase user's interest/profiles to user and visitors.
It's not a replica of canvas view.

Our limits are large enough to allow you to publish tweets that the user makes. I am assuming a reasonable user can do no more than 100 tweets a day. The limits are large enough to allow you to update at this rate.

[Badaro]

One final question about this: Do you have a date for when you're
going to remove HttpRequest? I need to know this to plan the
migration.

Even if you don't have a specific date to give, something in the lines
of "No earlier than <insert data here>" would be enough.

Filipe Badaro

[Apurv Gupta]

No sooner than 15th June, and we'll give you at least 2 weeks heads up. Hope that helps.