Okay I went through fusion in detail. I don't see a reason why you can layer hessian on top but on the same hand I'm not sure its required right now. I've played with fusion a bit and I'm pretty happy with it. Only one question.
Right now the way to get the fusion world is via knowing its index which is stored in a enviroment variable or given on the command line. I assume this is pretty much the only way so on the case of me adding a new shared world for application we simply need a new environment variable. Or we can easily connect intially to the main world to get the index of a secondary shared world. It would still need to be created in the master process ? Mike On 12/31/05, Mike Emmel <[EMAIL PROTECTED]> wrote: > On 12/31/05, Denis Oliver Kropp <[EMAIL PROTECTED]> wrote: > > [EMAIL PROTECTED] wrote: > > > On Fri, 30 Dec 2005 21:45:30 +0100 > > > Denis Oliver Kropp <[EMAIL PROTECTED]> wrote: > > > > > > > > >>Mike Emmel wrote: > > >> > > >>>On 12/30/05, Ben Combee <[EMAIL PROTECTED]> wrote: > > >>> > > >>> > > >>>>DirectFB already uses Fusion for shared memory access and IPC, so it's > > >>>>probably something you should consider. > > >>>> > > >>> > > >>> > > >>>I'm a bit concerned about sending application level messaging via > > >>>fusion. > > >>>Generally its for fairly critical messages. There is little control > > >>>on how much messaging the applications will do. > > >> > > >>We can have a separate Fusion World for Application Level IPC. > > >> > > >>It would use another Fusion Device, Dispatcher Thread and SHM Pool. > > >> > > >>-- > > >>Best regards, > > >> Denis Oliver Kropp > > >> > > > > > > A question here can be how is unique intented to work and how will unique > > > read/write properties (like the fact that an application gets raised or > > > lowered, or the fact that an application sets an emergency hints because > > > it reclams the attention of the user, wich generally result in an apps > > > changing his color in the taskbar,...) and how it will communicate with > > > the other apps. > > > In the X11 world, this kind of thing is done by getting/setting (named) > > > properties of each window. Is it possible to do the same kind of things > > > with fusion? (and how?) > > > > This basic mechanism can be added to the CoreWindow, but is that all you > > need? > > > > Thats pretty close to all X11 does for Atoms but you also need to > support something like XClientMessageEvent. > > I'd really like to just implement this > http://www.caucho.com/resin-3.0/protocols/hessian-1.0-spec.xtp > > On top of fusion for the transport. > Its almost the smallest generic serialization/messaging protocal you > can have. I'm pretty confident we can build arbitray messaging api's > on top. > > For example we could even support the full X11 protocol with a message > converter listening on the wire. > > Mike > > > -- > > Best regards, > > Denis Oliver Kropp > > > > .------------------------------------------. > > | DirectFB - Hardware accelerated graphics | > > | http://www.directfb.org/ | > > "------------------------------------------" > > > > _______________________________________________ > > directfb-dev mailing list > > [email protected] > > http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev > > > _______________________________________________ directfb-dev mailing list [email protected] http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
