At 13:26 20.07.99 -0600, you wrote:
> I need to figure out a good way for a mapbasic application to
> communicate with another computer over a Windows/NT network. One
> computer is receiving GPS signals from remote "units", and
> dumping these in an Access database. ...
> I know DDE is passe now, but it seems so odd to me that MS
> provides so little support for direct network communication, that
> I must be missing something. How DO you talk over a Windows
> network? And how do I do it with mapbasic? Anyone have any ideas?
I have used so-called "named pipes" for bi-directional client-server
communication in a Windows network. This mechanism is part of the
WinNT API (does also work with UNIX systems) and are somewhat easier
to implement than TCP/IP sockets. Win95 support is limited to the
client side functionality. To make use of named pipes you would have
to write a DLL or EXE module (preferably in C/C++) that is run
concurrently with MI and communicates with your MB app the usual
way ("integrated mapping").
Related Win32 API calls are: CallNamedPipe() / CreateNamedPipe() /
TransactNamedPipe() / WaitNamedPipe() ...
Good luck.
Regards,
Christian Singer
Ing.-B�ro
Christian Singer
Singerhoffstr. 14
D-44225 Dortmund
Germany
E-mail: [EMAIL PROTECTED]
WWW : www.icsinger.de
Phone : +49 231 791464
Fax : +49 231 791460
----------------------------------------------------------------------
To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put
"unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
