|
From: Artyom B. <ar...@z2...> - 2003-03-19 14:08:30
|
you keep on answering outside the list aren't you? On Wed, Mar 19, 2003 at 01:28:24PM +0100, Simon de Bakker wrote: > > 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). > > aye, that's sort of how I looked at it now :) > goody :) and GUI can reuse this later. > > > > 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? > > During the pipeline creation simca should find out whether the link is > local or remote, maybe even what type of link objects support > (udp,tcp,..) and ask for hints. Depending it can decide what way is best for this link. > yes this sounds like interesting strategy. i was thinking to make it more automagic - like every server has a number of connectors that would listen to incoming data and server decides which connector to use for every incoming remote link balancing the load of every connector. but hinting can help - actually at the connection establishing time server knows nothing about the load - that's what one could hint. something along these lines |