On 16 Jul 2007, at 10:14 AM, Hans van der Maarel wrote:
The overhead is definately going to be more than what it would be when using a direct link in the workspace. Also, this requires the computer to act as a server, something that's probabely not allowed in most corporate networks...
There are server processes running on every (modern) computer, so this shouldn't be an issue in this case. Since it is set up to listen only on "localhost", presumably no other computer can connect to the port anyway.
I guess that could happen if a receiver starts listening before the appropriate transporter starts sending
I believe the receivers all listen asynchronously and queue up the features for further processing by FME's main processing chain. The receiver is never "stuck" waiting for features, so it shouldn't be able to hold up processing.
What can I say... I just like to use FME in impossible ways ;)
That's what computers are for, right? -g
