Update on 3.1.x

[Alex Grönholm]

Work on the 3.1.x branch has progressed yet again.
I added some lines to the task list, based on features I've added.

IPv6 support was added, although finding services from an IPv6-only
registry server is unlikely to work.
Also, forcing either IPv4 or IPv6 in a dual stack system is not yet
supported in the command line tools.

RPyC's internal logger module was scrapped, and the standard library
logging module is used instead.
Some effort has gone into maintaining similar logging options as in the
3.0.x branch, but this needs more testing and polish.

Last but not least, I'm going to make authenticators chainable, so you
can combine them in any way you want, like tls+compression+user auth (in
theory).
How this is going to be implemented is not yet clear, but I'm constantly
learning more about RPyC's internals.

Constructive feedback and questions are welcome.

The current status of the branch is:

- Restructure the project to more "standard" form (done)
- Reformat the code to be PEP8 compliant (done)
- Add Python 3 support
- Add Jython support
- Add IPv6 support (done)
- Leverage Distribute/Setuptools support to install command line scripts
for launching servers (done)
- Convert the test suite to use nose (done)
- Remove the rpyc.lib.logger module in favor of standard library logging
(done)
- Finish the work on the new security layer

As before, the branch can be seen at http://bitbucket.org/agronholm/rpyc/

[Antoine Boegli]

I have a request, perhaps I can even implement it myself :

I need to be able to know more about the services registred by the reg
server than it is published actually, e.g. the service "class name".
For example, I need to know to which "application" the service apply,
or which kind of datas it can access. A kind of "topic list", created
at the instance level instead of the classe level, would be very
helpfull.

Howver, if this is not acceptable for the base framework, I can add
this to a subclass of the registry servers.

2009/10/24 Alex Grönholm <alex.g...@nextday.fi>:

--
Antoine Boegli
software engineer & linux expert

[Alex Grönholm]

Antoine Boegli kirjoitti:

> I have a request, perhaps I can even implement it myself :
>
> I need to be able to know more about the services registred by the reg
> server than it is published actually, e.g. the service "class name".
> For example, I need to know to which "application" the service apply,
> or which kind of datas it can access. A kind of "topic list", created
> at the instance level instead of the classe level, would be very
> helpfull.
>
>

Not sure what you mean, but perhaps you can elaborate with a detailed
example?

[Antoine Boegli]

I need to run more than one set of identical services, but for
different contexts. For example if I have an application with a
database, a mail server and some other ressources accessed by rpyc
services, but I need to run all that for two or four different
customers. I could make the difference at the service level, but it
seems to be more complicated than having a way to tell for which
context an rpyc request has been made. In my case, there is an OpenERP
server with a set of customers databases, that I need to access from
different points with different credentials.

2009/10/31 Alex Grönholm <alex.g...@nextday.fi>:

--