AniDB

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.

blame rar. hehe. (will fix it asap)

Keeper of Demons wrote:Please, may we have back a style similar to the alternate style from the old AniDB ?

u mean this http://petriw.com/creativity/rar/css/brown2.css ?

hehe, yeah. it did actually try to check the header, but it failed with a null pointer exception...

i have already fixed webaom. (did it silently, hoped no one would notice the bug, hehe)

i don't think it has anything to do with HT. i'm running it on P4 2.8 HT. no problems. maybe it has something to do with Windows (Server) 2003 SP1? dunno, never used it.

'Use AniDB default' will give u things like 'S9001', but 'Use Rules' work fine (well u have to define a schema before u can use it). the problem is in the server code. i'll will fix that.

gzip is enabled again. i'll release a new version later today.

the TCP protocol is not public.
search for 'tcp' in this forum
http://www.anidb.net/forum/viewtopic.ph ... hlight=tcp

are you using api.anidb.info? (not anidb.ath.cx)

you have to give some more info if you want help. some code would be helpful

this will be fixed in the next version of the server. (the storage field will not be truncated on aredhels example)

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. Curre...

u can't ping a specific port. i meant the udp-api PING command. a spimple way to test the connection is to use the ping button in webaom. anyway.. check out ExElNeT's client http://www.anidb.net/forum/viewtopic.php?p=19138#19138. it is open source. (unpack the jar)

My guess is that after I send my AUTH string over a socket, I should call recv and expect data from that same socket. Is this true for UDP and TCP in general? That is true. I tried setting different delays between sending my AUTH string, and recv'ing, but no luck on that either. No need to wait, bu...