[solved] DevNet API disabled for a while

ucomesdag

[quote author="ZapB" date="1304500975"]Is any troll apart from Marius able to check this whilst Marius is on hols please? How are the API requst levels now and can they be reinstated please?[/quote]
I second that!

mgran

Greetings from a beach bungalow in San Diego :)

!http://dl.dropbox.com/u/217336/varnish_request_rate-month.png(graph)!

We're still seeing volumes of API traffic way above normal. It´s trending downwards though.

ZapB

OK Marius. Thanks for the update. Enjoy your hols :-)

ucomesdag

[quote author="mariusg" date="1305002565"]Greetings from a beach bungalow in San Diego :)[/quote]
Some much needed sunshine? ;-)

mgran

The stats are not going down as we have hoped, so I suggest we do a +1 on the API version and provide it on a new unblocked URL.

From http://developer.qt.nokia.com/qtapi/0/* to http://developer.qt.nokia.com/qtapi/1/*.

We would then stop /0/ in the firewall and consider it forever unavailable.

Yay or nay? :)

andre

It might be a good idea, but there is nothing to stop this from happening again. Would it be a good idea to hand out API keys for apps to use? That way, you can at least monitor what application is causing trouble.

DenisKormalev

Andre, do you mean something like OAuth?

andre

I don't know much about OAuth, so I would not know. What I mean is that as a developer working against the API, you would request a unique key to use for your application. You would append this key to your requests as an additional parameter. The API would only respond if the API key is valid, and give an error otherwise.

I think Google uses something like this to keep track of the use of their services. It can also be used to limit the number of requests for a specific application of the API.

DenisKormalev

Yep, agreed with this suggestion.
Also it will be good to have devnet auth in new api :)

ZapB

Welcome back Marius. Yes an API key would be a good idea.

Marius, can you tell from the logs what user-agent or ip blocks are causing the problems?

mgran

We have opened up v1 of the API now:
http://developer.qt.nokia.com/qtapi/1/member/profile
http://developer.qt.nokia.com/qtapi/1/forums/posts/unread

No API keys needed yet, but we're evaluating that as a good idea for the future.

v0 of the API is still getting hammered.

ZapB

Excellent. Thanks Marius. I'll update my client over the weekend and give it a test drive. Have a good weekend.

mgran

[quote author="ZapB" date="1307111488"]Excellent. Thanks Marius. I'll update my client over the weekend and give it a test drive. Have a good weekend.[/quote]

Same to you! I've mailed Vass with the update, so he can test his plugin - and maybe we can be back to normal.

andre

The badges list in the http://developer.qt.nokia.com/qtapi/1/member/profile result is incomplete.

mgran

[quote author="Andre" date="1307112808"]The badges list in the http://developer.qt.nokia.com/qtapi/1/member/profile result is incomplete. [/quote]

Indeed, the old badge handling code outputs there, we shall fix.

andre

[quote author="mariusg" date="1307112890"][quote author="Andre" date="1307112808"]The badges list in the http://developer.qt.nokia.com/qtapi/1/member/profile result is incomplete. [/quote]

Indeed, the old badge handling code outputs there, we shall fix.[/quote]
Man, you're quick to respond! :-)

mgran

It's close to the weekend, I'm already done with the bug report for this issue :p

ZapB

Hi Marius, I have my client working with the new API. Now to add some new features.