Echelon OpenLNS - Manual (Page 716)

OpenLNS Programmer's Reference 679
connections are updated.
You should not set this value to True
because your application may then
process or send network variable
updates using inconsitent network
variable configuration. This could lead
to misinterpretation of network
variable updates on this or another
device.
16 lcaFlagsUseTCP
Indicates that a remote client (see
RemoteFlag) will access the OpenLNS
Server via TCP/IP. This flag should
not be ORed with the
lcaFlagsUseNSI (32) flag.
32 lcaFlagsUseNSI
Indicates that a remote client (see
RemoteFlag) will access the OpenLNS
Server via an NSI over a L ON W ORKS
network. This flag should not be ORed
with the lcaFlagsUseTCP (16) flag.
1024 lcaFlagsDirectCallback
Enables callback routines (event
handlers) to be executed from an
internal LNS thread, as opposed to the
thread that instantiated the Object
Server. This essentially turns your
application into a multi-threaded
application. Executing event handlers
from non-client threads in this fashion
is often more efficient.
By default, this flag is not set.
However, the ability to execute
handler routines is not supported by
all development tools. It is supported
by Visual C++ and Microsoft Visual
Studio .NET, but not by Visual Basic.
In addition, there are several
important programming
considerations you need to be aware of
when using multiple threads within an
OpenLNS application. For more
information on multi-threading with
OpenLNS applications, see the
OpenLNS Programmer's Guide.
2048 lcaFlagsManualNsdUpgrade
Indicates whether client’s Network