Re: Messaging system

[Christian Reiniger <warewolf@mayn.de>]

Adrian Ratnapala wrote:

>> >hand we can always add this functionallity in later if we think we need it.
>>
>> As adding this functionality would alter the specified behavior (programmers have to be able to rely on this behavior) I´d think thrice before doing this.
>
>No it doesn't change any behaviour, I should have made that clear.  We just extend the API with specializedversion of connect() which connect to receivers

Yep. of course. I actually wrote such a suggestions some lines above - and immediately forgot it ;*)

>> I currently try to synchronize all changes with the Gtk-- team, so both systems will have the same behavior, same features, same handling
>> - just different naming schemes. I think this is a good solution.
>
>Well, you're the one who has to maintain the code, so I guess its your call.

As long as there is no "standard" signal/slot mechanism we´ll have to stick to our own naming scheme, I fear...

>> >If there was a common, free library out there, I would
>>
>> It definitely is a neat idea. I love it. A bit like a mini-CORBA, having PPlay monsters interface to Gtk gauges etc.
>> Neat.
>
>Yeah, OO is cool.   None of this overlaps with what CORBA does though.

Yep. I tried to express that it´s quite similar to CORBA - both interface completely independent parts of code.
CORBA works usually at Application level, while a signal/slot mechanism is used at component level

>I must say I am a little surprised you like the idea, I just put it up as a throwaway "crazy idea".

Well, such a mechanism is needed in almost every modern code - so why not (1) make it reusable and (2) make it standard?

>But  if you like it, I suggest you talk to the Gtk-- people about it and then put a joint post
>onto comp.os.linux.announce and other places, and get the project going.

I´ll talk to the Gtk-- people, but my news system is currently broken (and will remain so for some time), so c.o.l.a. is unreachable for me...

Cu
	Christian