I wrote a Chii forwarding script for mirc last night, looking to later use the UDP interface to do some of the Chii type functions. Basically it gives access to users on another network the without login Chii triggers, by relaying the message across and returning the answer. So, same load as if they were on the channel.
Now, this is stupidly simple, even coping with the silly scripting language. But, as the udp docs state, exp really wants these kind of commands to be done from disc. So, the logical step forward would be to read the AOM files. However, decripting, then searching though a multimeg database using a language that complains endlessly about whitespace and newlines appeals to me less than just chucking strings around, so I'm killing it here.
The curious can join #bay12games on WorldIRC and use "c!help" style commands, and I'll send the devs code if they want it (not much point).
Rar
MiniChii
Moderator: AniDB
well,
using a full db dump for something like an irc bot does seem to be overkill in deed :o)
and it's also not really needed as the main reason for using db dumps is a large number of users or rather installs.
an irc bot normally doesn't create that much load, so it could well run on top of the udp api.
however right now the udp api isn't ready to be used for something like this (the commands are simply not implemented). I guess you can keep things as they are as long as you're not overloading chii (make sure you include some kind of flood protection, i.e. forward only one request every 3 seconds to chii, or something like that)
BYe!
EXP
using a full db dump for something like an irc bot does seem to be overkill in deed :o)
and it's also not really needed as the main reason for using db dumps is a large number of users or rather installs.
an irc bot normally doesn't create that much load, so it could well run on top of the udp api.
however right now the udp api isn't ready to be used for something like this (the commands are simply not implemented). I guess you can keep things as they are as long as you're not overloading chii (make sure you include some kind of flood protection, i.e. forward only one request every 3 seconds to chii, or something like that)
BYe!
EXP
Ehehe, yes. Basic arse flood protect is in (as in, only one command at once, so Chii is exactly as fast as she wants to be). But, plan to have sessions etc. for users, so will be smoother for any 'release' version.
Anyway, I've been spamming the anidb udp port all evening, trying to get it to respond. Then I worked out I wasn't listening to the right thing... ;_;
Anyway, working login/out, so I might be requesting udp features soonish.
Rar
Anyway, I've been spamming the anidb udp port all evening, trying to get it to respond. Then I worked out I wasn't listening to the right thing... ;_;
Anyway, working login/out, so I might be requesting udp features soonish.
Rar
I have been thiking about having a "mini-chii" as well, but I considered implementing it using the TCP API, but only implementing certain functions. Specifically, not anything related to file-data nor mylist data, so basically the only commands would be !anime, !group and !episode. (!episode would show some information about an episode, like title and length.)
UDP currently lacks functionality for the basic stuff you'd want for a proper udp minichii atm unfortunately, and tcp is not open. The good thing is that it's very easy to program a pocketchii like mine. Peli did one after seeing mine, and I just gave Caster some code for the same. The good thing about this is that as it's just forwarding it's intrinsicly safe, so there aren't the same worries as there would be over bad tcp implimentations.
Rar
Rar