FFConnectionManager switching

[Tor Tveitane]

Hi,

Some of my apps works in on of three modes:

TCP-IP Client
InternalProt + TCPIP Server
InternalProt with no exposed Server

What is the best / safest way to start/stop the internalserverengine /
externalserverengine in conjunction with changing the FFCM modes when
switching between between these three modes in runtime?

I have browsed the ng postings about ffcm but not found something covering
this scenario, sorry if I overlooked something..

regards

Tor

[Eivind Bakkestuen [TPX]]

I would actually recommend that you use the connman only in the first
scenario (regular client), and use a standard legacytransport for the second
scenario where you expect incoming connections. I don't think anything wrong
will happen otherwise, but I'm not making any guarantees. The connman is
designed for client-side use.

Is there any other way of stopping the serverengines than calling
se.Shutdown? I don't know. <g> I would set client.active to false, then
transport.enabled (if applicable) to false, shutdown serverengine, then
activate the other session (and thus activating the rest of the component
chain).

--

Eivind Bakkestuen [TPX]

Please, no private email unless requested.
This newsgroup is searchable at http://www.tamaracka.com
Visit TurboPower's new Foundry at http://community.turbopower.com

"Tor Tveitane" <news...@bushsoft.com> wrote in message
news:at8jba...@bushsoft.net...