Association Subscribers Manager and Open source stuffs - Tag - slackget10

slack-get perl module change its name !

2007-12-03T07:32:00+01:00

Hi,
Like I announced on the developers' mailing list, the slackget10 was about to die. It's now done. The PAUSE (Perl Authors Upload SErver) admins sent me an email confirming the creation of the Slackware::Slackget registered namespace on PAUSE/CPAN.
I will modify all the library to fit the new namespace and release the changes as soon as possible.
One more thing : I created a new branch on the SVN for the GUI tests

Cya,

Arnaud Dupuis

New Network backend mechanism

2007-11-27T21:32:00+01:00

Today I implemented the new slackget10::Network mechanism I wanted to. What is it you ask ?
Clearly something which will help everything to be super-easy to improve. As you may know (or not) the slackget10::Network Perl Module has been completely redesigned and will be largely recoded.
The changes are quite important and the API is completely new. It's now a front end module (like slackget10::Network::Connection is) and it aim at providing a unified interface for all kind of "protocol" implementation.
The idea is to answer the question : "what are you doing with an incoming network packet ?". The answer is simple : you decode it, you interpret it, you build the answer and you encode the answer before sending it. Hi,
Today I implemented the new slackget10::Network mechanism I wanted to. What is it you ask ?
Clearly something which will help everything to be super-easy to improve. As you may know (or not) the slackget10::Network Perl Module has been completely redesigned and will be largely recoded.
The changes are quite important and the API is completely new. It's now a front end module (like slackget10::Network::Connection is) and it aim at providing a unified interface for all kind of "protocol" implementation.
The idea is to answer the question : "what are you doing with an incoming network packet ?". The answer is simple : you decode it, you interpret it, you build the answer and you encode the answer before sending it.
Very well ! the new API behave exactly like that and you can test it with the last SVN revision of slack-get trunk (83) and the following code :

#!/usr/bin/perl

usestrict;

usewarnings;

useslackget10::Network;

my$net = new slackget10::Network ;

my$message = $net->decode('<?xml version="1.0" ?>'.

'<SlackGetProtocol version="1.0">'.

'       <Enveloppe>'.

'              <Action id="123456">get_connection_id</Action>'.

'     </Enveloppe>'.

'</SlackGetProtocol>');

print$net->encode($message), "\n";

I think it's quite a natural of of doing things. Of course, the sg10::Network class provide the interpret() method !
And to actually do the encoding and decoding part it rely on slackget10::Network::Backend::* class.
I already coded the slackget10::Network::Backend::XML backend and do not plan on coding other backends until I have decided how to implements secure connections.
I will work on tutorials/howto which will describes how to code network backends and add the support for new protocol for the slackget10::Network::Connection class.

See ya !

Arnaud Dupuis

New slackget10 Perl Module release - version 0.11

2007-11-11T21:21:00+01:00

Hi,

Well.. I changed so much slackget10::Network::Connection* modules that I made a release of the whole module on CPAN !
This release features :

Dynamic driver loading. As explained in another post I made the driver loading code completly dynamic. From now on, you just have a slackget10::Network::Connection::<PROTOCOL>.pm module to add support for <protocol>:// protocol to slackget10::Network::Connection.pm.
New slackget10::Network::Connection API. Loads of things have changed in the API of this class. First it's now event driven and it means you have to pass a InlineStates => {} parameter to the constructor. Then the old construction behavior (with only one parameter) is now deprecated and unsupported. Please have a look at the documentation for more information about this.
New slackget10::Network::Connection::*.pm API. It's now way easier to create a protocol driver ! You just have to create a module with the 3 followings methods defined inside : __test_server(), __get_file(), __fetch_file(). They'll be called by slackget10::Network::Connection.pm wich will take care of everything (like event throwing).

This class is now fully usable out of the box in other programs than just slack-get, and that was one of the goal of the slackget10 module !
I'll made a HOWTO on the wiki to explain how to create a driver.

Good day

Arnaud Dupuis

Week end planning

2007-11-10T15:46:00+01:00

Hi ,

I'm working a lot on slack-get this week end ! Today's morning was concentrated on slackget10::Network::Connection modifications. I made quite a lot of them. I made two major changes in the module architecture :

I made the protocol driver's loading completly dynamic (no more static, hardcoded hash table to track authorized protocols)
I changed all drivers (slackget10::Network::Connection::*) and made them independents from the slackget10::Config. The "config" parameter is not required anymore. In place of this option you have to give the "download_directory".

The other thing I planned for the week end is to polish my skills with Qt4. I'll try to make the configuration widget for the GUI this week end... even if I can't promise anything.

I also updates the Wiki by creating some API documentation pages.

Let's keep the pace !

Arnaud Dupuis

new release of the slack-get Perl Module - slackget10-0.10

2007-10-24T06:50:00+02:00

Hi all !

After doubt and interrogation, even after I though to dismiss the slack-et project it couldn't be helped... I enjoy developing this tool !
So be it. Here is the latest release of the slack-get Perl Module. Tons of thing are new since there was a not-released version...
This release main features are :

loads of bugfixes (starting with the test suite)
removed unused modules
removed deprecated modules

Well a lot of things !

I'm now working on the slack-get communication protocol. This protocol is full XML based and have to be well designed to support all situation of usage.
It also have to be bulletproof and highly error resistant.

By the way the slack-get devel mailing list have open, please find more information on this at Sourceforge , you can also find more informations about slack-get SVN on Sourceforge.

You can find all documentation and source of the new version of slackget10 on CPAN

That's all for the moment.

Good day

Arnaud Dupuis