UDP API Development

[epoximator]

Exp has handed the development of the udp server over to me. The first step is to update the api definition, i.e. v.0.03. I thought it would be best to let everyone who cares about the upd server participate in this work. When the spec is final, exp has to approve it before I can implement it.

Current spec (v2):
http://www.anidb.net/wiki/index.php?tit ... Definition
First draft of v3 (add-on to v2):
http://www.anidb.net/wiki/index.php?title=UDP_API_DEV
Feel free to edit these pages. (Only layout / typos in v2, though.) Keep in mind that the udp server is only for retrieving small amounts of data. So what should definitely not be added are ways to download complete dumps of anime/ep/file/mylist/... data. Including everything that chii can do should be ok.

I have also compiled a list of every client registered in this thread. Please do update the status (and other info) for your client. (Keep it simple and mind the current format.)
http://www.anidb.net/wiki/index.php?title=UDP_Clients

[fahrenheit]

i would sugest 2 things regarding the v0.0.3 specs:
- first, create a separate thread for discussions to it;
- second, what what the new comands do? (some are easy, but a small description would be nice)

[Rar]

Split, done. As for what you want the commands to do? It's a wiki. Edit it. Then make epoxy impliment it. Personally, I want a command I can chuck sjis/utf8 at and get aids back.

Rar

[Edit... pluralising 'aid' seems dangerous....]

[PetriW]

Just html escape it and you can search for it.

[Rar]

Converting between encodings is a non-trivial task in various languages that you'd want to write a client in.

Rar

[PetriW]

Converting between encodings is a non-trivial task in various languages that you'd want to write a client in.

If you know the codepage. It least the anime titles are in ascii though.

[epoximator]

a v3 test server is up and running at port 9001.
- protover=2 is still used
- developers must register their clients here before they can access it

i have updated webaom for this ver. (it's possible to access the api directly with it)

it's of course not to late to change stuff in the spec.

[exp]

just to keep you updated:
the v3 server (with protover=3) is now running as official server on port 9000.
remember to register your client, otherwise you will not be able to AUTH successfully!

please report any bugs you find to epoximator.

BYe!
EXP

[W1N9Zr0]

290 NOTIFICATION seems to be mixing up notifies and messages since the switch to v3, though it's not documented in the API
Which one's correct?

EDIT:
Also, issuing NOTIFYLIST when there're no notifies/messages gives 600 INTERNAL SERVER ERROR, which wasn't the case with v2

[epoximator]

confirmed. thx

will be fixed on next update

[fahrenheit]

you are missing a return code on the wiki or the return code for client banned is diferent?

555 BANNED
Connection limit reached.

i got that while testing, my fault, i forgot to set my list port, instead i used a random port.

[epoximator]

wiki updated:
http://wiki.anidb.info/w/UDP_API_Definition#General
read the note
thx

[fahrenheit]

wiki updated:
http://wiki.anidb.info/w/UDP_API_Definition#General
read the note
thx

lol, thanks man, it helped

[fahrenheit]

has the PING command begun to require auth?

i got a 501 LOGIN FIRST to a PING query.

[epoximator]

the latest version (updated today) has some changes in the parsing code. yeah, you could call it a bug... anyway, append a space or make sure that nothing else follows commands without arguments. ('PING' and 'PING ' will work, not 'PING\n'). this will be fixed on next update, back to the old behavior