|
From: Artyom B. <ar...@z2...> - 2003-03-19 12:14:39
|
On Wed, Mar 19, 2003 at 12:34:47PM +0100, Simon de Bakker wrote: > > but they said in that docs > > (it's in ORBit beginner's docs, section about echo client, find it) that > > fist you have to enable TCP/IP in orbit configuration. could you please > > find that out and test and report sucess? :) > > yup > okdan. the sources i've sent were non-compilable, but i guess you fixed the little bugs :) > > > > i'm not thinking about corba and gui at the moment but about distributed > > simca's and i think we can build that functionality on top of corba and > > we can easily connect corba to existing gsimca stuff. have a look how i > > connected a list to CorbaTest server. > > I only doubt the use of corba for control and media streams, because of > overhead. But I don't know how serious that is. Maybe we should try out. look at it like this: the simca is a CORBA server that provides interface allowing to instantiate objects, connect them destroy them, create containers and move object from one container to another (construct pipelines in other words). simca_object_t is visible as CORBA server that allows to assign / request properties, execute commands etc. once pipeline is created it functions like it used to (like it does in a current version), not touching any CORBA things, unless there's a link to an object far away, in which case something should be different. but what? i guess the event handler that is called once object emits something on a outlet-property should be different. and this handler should be installed during simca_objects_connect call if the receiver object is remote. and again this handler shouldn't use corba mechanisms, but should remain simca-specific. i send this to the list for it is worth archiving :) cheers, artm |