First public pre-alpha Client available

Post by **exp** » Mon Jun 16, 2003 8:39 pm

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

Pixel_K · Post by **Pixel_K** » Tue Jun 17, 2003 11:14 am

System.security.SecurityException on start
address Anidbclienttest3.Form1..ctor

Windows 2000 SP3 - French

Post by **PetriW** » Tue Jun 17, 2003 12:31 pm

Post bugreports here:
http://www.anidb.net/forum/viewforum.php?f=13

DonGato · Post by **DonGato** » Tue Jun 17, 2003 5:51 pm

exp baka!
Using MS.NET for this!
/me angry at exp.

kidan · Post by **kidan** » Tue Jun 17, 2003 8:05 pm

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

Post by **exp** » Tue Jun 17, 2003 8:10 pm

DonGato wrote:exp baka!
Using MS.NET for this!
/me angry at exp.

I'm INNOCENT!

after all it's not /me who's working on that client!

BYe!
EXP

kaoru · Post by **kaoru** » Thu Jul 03, 2003 12:37 pm

i wont install .NET on my pasocon so will there be an version out in the future which will run without installing unnecessary shit?

Post by **exp** » Thu Jul 03, 2003 4:14 pm

well,

there is a simple solution, write one yourself

BYe!
EXP

darkfader · Post by **darkfader** » Thu Jul 31, 2003 7:01 pm

100 WELCOME TO THE ANIDB API SERVICE
yay!
Hmm... interesting SQL queries

Maybe XML looks a bit safer.

Post by **exp** » Fri Aug 01, 2003 9:49 am

darkfader wrote:100 WELCOME TO THE ANIDB API SERVICE
yay!
Hmm... interesting SQL queries
Maybe XML looks a bit safer.

SQL? the api is not SQL related.
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

darkfader · Post by **darkfader** » Sun Aug 03, 2003 5:13 pm

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.

Post by **exp** » Sun Aug 03, 2003 8:25 pm

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