| Nicholas Perez 2007-04-30, 7:18 pm |
| Just from an ease of use standpoint, maybe have the ability to store
"default" domains and trackers as arguments to spawn. Simplifying the
input always helps.
And of course, bringing the MogileFS::Client a little closer to POE
would be an improvement. So instead of having discrete tasks to pass
on, expose the methods from MogileFS::Client as events, and then
manage all of the concurrency transparently as a pool of Clients to
reuse and round robin them or whatever.
All in all, from my really short glance at the code it is simple and clean
HTH
On 4/30/07, mock <mock@obscurity.org> wrote:
> I just released POE::Component::Client::MogileFS onto CPAN on Friday. It does
> what I need it to do, but since it's my first POE module, I'd certainly
> appreciate feedback if I'm doing stupid things ;).
>
> If you don't know what MogileFS is, you might want to look at
> http://www.danga.com/mogilefs/
>
> mock
>
|