First public pre-alpha Client available
First public pre-alpha Client available
Well, it's finally here,
a first version of an anidb client by Hisoka[].
be sure to check it out.
http://www.anidb.net/client/
Please post comments and bugreports in either the client feature request or client bugreport sections.
BYe!
EXP
a first version of an anidb client by Hisoka[].
be sure to check it out.
http://www.anidb.net/client/
Please post comments and bugreports in either the client feature request or client bugreport sections.
BYe!
EXP
Post bugreports here:
http://www.anidb.net/forum/viewforum.php?f=13
http://www.anidb.net/forum/viewforum.php?f=13
@dongato:
.NET is the wisest choice for an app like the anidb-client. This is because in .NET you have some great classes for async-databases and syncronisation via http.
.NET is the wisest choice for an app like the anidb-client. This is because in .NET you have some great classes for async-databases and syncronisation via http.
Last edited by kidan on Tue Jun 17, 2003 11:19 pm, edited 1 time in total.
SQL? the api is not SQL related.darkfader wrote:100 WELCOME TO THE ANIDB API SERVICE
yay!
Hmm... interesting SQL queries
Maybe XML looks a bit safer.
btw. please don't screw witht the api you might make the service unavailable to regular users if you do make a mistake there.
And XML is just bloatware.
BYe!
EXP
the API supports different compression styles, bzip2 is recommended, however no client supports this so far. And it won't make a big difference speed wise.darkfader wrote:Oh, whatever. But I saw some SELECT statements in the source-code, so that's why.
I don't have intensions to screw up, but is it really that simple?
Do you use any compression at all? Accept-encoding: gzip, deflate ?
It might speed up the updating.
the mayor problem with the current .NET client is it's local db, it's way to slow. but that will change in the next versions )
and btw. that select belongs to the internal data storage of that client, it has nothing to do with the API.
@screwing up, well not really but playing with the api might lead to availability problems for other clients. you should not be able to corrupt any real db data via the api though.
BYe!
EXP