|
From: Simon de B. <si...@z2...> - 2003-03-19 14:29:36
|
On Wed, Mar 19, 2003 at 03:03:39PM +0100, Artyom Baguinski wrote: > you keep on answering outside the list aren't you? you got me; little mistake, pressed 'y' to fast... > > 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. The hinting I introduced because different objects may favor different types of connections. So does a stream object need a reliable tcp connection and support for larger packet sizes than does e.g. a realtime sensor input. For the latter it might not be a problem if it loses some packages along the way if it is delivered as fast as possible. This is known by the object and can hint the connection mechanism. The object itself actually doesn't care how it is done, it might use tcp because the connection mechanism finds the other end needs it, but if needed it can demand. This means objects demanding different connection types cannot connect (unless used with a converter object ?). > something along these lines > -- Simon de Bakker \/01|)7 workgroup: http://www.void7.org personal homepage: http://www.josos.org |