p2psp team mailing list archive

[JP <jp.garcia.ortiz@xxxxxxxxx>]

The point is that I'm not sure we really need dynamic inheritance in
P2PSP... that makes difficult to write a port using a different
language. But, for the time being, I think we can continue with your
solution that, as I said, it seems better than what it was used
before.

2015-06-28 11:27 GMT-04:00 Max Mertens <max.mail@xxxxxxxxxx>:
> Hi Juan Pablo,
>
> On 27.06.2015 18:18, JP wrote:
>> Well, I can understand the warning said in [3] but, taking into
>> account that both solutions do not seem too much "pure", from the
>> traditional point of view of the OOP, your proposal Max is much more
>> elegant and simple. Good idea.
> Ok, thanks. Also I think the implications mentioned there do not affect
> the P2PSP code, as it is very clean and does not rely on those special
> semantics of Python.
> Another possible implementation would be overriding __getattr__ and
> delegating methods to base classes, but then for each peer there would
> exist multiple instances as well.
>
> Regards,
> Max
>