Handle bot status and queueing

[Freedos]

If I tested correctly following situations aren't handled:

1. Bot replies "All Slots Full, Added you to the main queue for pack"... -> Suggested behaviour: Wait until donwload starts
2. Bot replies "All Slots Full, Denied, You already have that item queued" -> Suggested behaviour: Check for the instance that queued the item and request again when this is finished.
3. In general it would be usefull if the utility gives back more status massages. But maybe I'm just missing the correct way communicating with you tool :-). I'm trying to use it with SB.

It would be nice if could consider these suggestions.

[JanGe]

maybe I'm just missing the correct way communicating with you tool

For now xdcc is more meant to be a stateless one-shot utility.

I currently just don't see a proper way to implement support for XDCC bot queues that does not rely on the specific wording of an IRC message.

There are however two rather simple changes that could improve usage of xdcc in this scenario a lot:

• Add a command line option to specify the length of the time to wait for a file offer by the XDCC bot
• Send an xdcc cancel message when xdcc aborts

In general it would be usefull if the utility gives back more status massages.

What kind of status messages do you mean? Exit codes when xdcc is aborting? Messages sent by a channel or bot?

I'm trying to use it with SB.

Doesn't ring a bell here. What is SB?

[Freedos]

Add a command line option to specify the length of the time to wait for a file offer by the XDCC bot Send an xdcc cancel message when xdcc aborts

both would be useful when using with another script

What kind of status messages do you mean? Exit codes when xdcc is aborting? Messages sent by a channel or bot?

I meant bot status messages like mentioned above without the verbos log so it's easier to read/pipe them

Doesn't ring a bell here. What is SB?

SickBeard

Nice work by the way. To bad it's written in haskell. Never got used to it.

[JanGe]

both would be useful when using with another script

Issues #6 and #7 now track these.

I meant bot status messages like mentioned above without the verbos log so it's easier to read/pipe them

Yes, there should be a proper logging facility added with support for levels of verbosity.

As different levels, I would propose

1. No messages at all (only progress bar)
2. Privmsg and Notice messages by the targeted bot
3. Privmsg and Notice messages by the targeted bot and joined channels
4. All messages

Nice work by the way.

Thanks. :)