[Rummble API] Error code 4

[Merdica]

Hello,

what means


<response status="fail">
<code>4</code>
<message>Application rate limit reached</message>
</response>

--
You received this message because you are subscribed to the Google
Groups "Rummble API" group.
To post to this group, send email to rummb...@googlegroups.com
To unsubscribe from this group, send email to
rummble-api...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/rummble-api?hl=en
For API Documentation, visit http://developer.rummble.com/docs

[Clive Cox]

There is a limit to the number of API calls you can do per day (5,000)
and the frequency (1 per second).
See http://developer.rummble.com/docs

From looking at the logs your app seems to be doing a setLocation call
once per second with the same parameters (including signature).

Clive

[Merdica]

oh, thats not good for me.
I want to make an Location service app on which friends can see each
other. but that only works when every persons send their actual
position(even with once per 5 minute it's too often with this limit).

On 7 Mai, 14:39, Clive Cox <clive....@rummble.com> wrote:
> There is a limit to the number of API calls you can do per day (5,000)
> and the frequency (1 per second).

> Seehttp://developer.rummble.com/docs

[Clive Cox]

The rate limit can be made more flexible or switched off on request.

However, before that I suggest you look further into the design of
your app.
Firstly, you need to look at why your app was sending an identical
setLocation once per second. Was this purely for testing? If so, fine.
I would have thought your app would update a person's location only on
significant change in position and that API calls to get people's
location would be more frequent that setLocation calls.

I'm sure other members of the Rummble team may have further
suggestions for you.

[Claudio Weeraratne]

Yes, I think an ad hoc update rate for the setLocation would be ideal (since it's also not so quick to execute).

Every N seconds/minutes you could check the Latitude/Longitude information about the current point.

If the distance between the current point and the previous point (that you have saved previously)

is above a specific threshold you can call the setLocation method, otherwise it means that the user didn't move significantly.

2010/5/7 Clive Cox <cliv...@rummble.com>

[Alex Housley]

Hi Merdica,

Am I correct in the understanding that your find friend implementation automatically triggers a simultaneous setLocation call from all friends?

How about showing the last known location of friends? This can be achieved by populating the user_ids parameter in user.getInfo with friend ids from network.getFriends.

To request current location from friends, it would probably be better to first send a notification to ask for a location update.

I hope this helps.

Cheers,

Alex