Re: [Pybeep-devel] Messages

[Sean A. <ze...@wo...>]

On Mon, 2002-01-28 at 10:04, Sean Allen wrote:
> Gabe
Actually it's so the library can differetiate between MSG's and others
(RPY, NUL etc) it all used to be inside channel but was broken out into
these classes. ATM, all this is inside channel.py, maybe we should also
consider breaking it out into Message class, and if that seems clunky,
make a MessageMSG class following the java object model.
Sean
> I've just noticed that the message impl class, Message is extended to
> the concrete class MessageMSG in the beepcore-j. I guess this is to
> allow people to subclass message with their own implementations, do you
> think we should follow this or just implement it straight in Message,
> for brevity?
> Sean
>=20
>=20