Ok, I think I figured out a proper solution, for clarity I will
reiterate the entire solution. It's a lengthy mail, but please do
read it and tell me what you guys think about it.
We want to implement a .defs file with control procedures, which can
ofcourse be independant of libchannel. The only
"Neal H. Walfield" <[EMAIL PROTECTED]> writes:
> I agree with Pierre, please provide some examples.
Ah yes, examples, examples. I've mostly been going by the following
passage from an old archive mail about libchannel written by Marcus
(http://people.debian.org/~terpstra/message/20020130.174030.
I agree with Pierre, please provide some examples.
I suspect that if an object implements a wider interface, then the
added methods should be written up as a regular mig interface file.
That's what mig is there for: the dirty work.
As the new routines extend the old interface, just call the basic
Scribit Carl Fredrik Hammar dies 09/07/2007 hora 22:04:
> we want to be able to dynamically load in channel classes into a
> channelio translater (at start-up) that can handle RPCs that are
> unknown by libchannel and channelio
Could you give examples?
Curiously,
Pierre
--
[EMAIL PROTECTED]
Open
Hello,
I'm currently thinking up how channel's control interface (a la ioctl)
will look like and I need some input.
I have a fairly good idea of how the backend will look like in
libchannel itself (more on this once the following is resolved.) But
getting dynamically extensible IPC for it is a b
