Thanks for your question.  Windows 3.1 currently doesn't support
TCP/IP natively, although there are several third-party TCP/IP
providers.  If you have an API to a TCP/IP DLL, you can use the aclwin
foreign function interface to load that dll and call its functions.

  The ipc functionality on aclunix is really just a wrapper around
some foreign functions to socket calls.  Although some work would
probably be needed to get something similar to work in aclwin, the
ipc.cl source is available with the aclunix emacs-lisp interface code
and may provide some assistance.

  Windows NT and Windows95 do have native support for TCP/IP, and so
it is possible aclwin may have interfaces to these in the future.

	Charley
---
Charles A. Cox, Franz Inc.        1995 University Avenue, Suite 275
Internet: <franz.com at cox>           Berkeley, CA  94704
uucp:     uunet!franz!cox         Phone: (510) 548-3600; FAX: (510) 548-8253
                                  WWW: http://www.franz.com/


> ACL/WINDOWS 2.0/Questions
> 
> We would need an interface to TCP-streams in ACL/WINDOWS 2.0. Ideally they
> should support both client and server connections.Since something like this
> is implemented for ACL/UNIX, is there any chance of an ACL/WINDOWS 2.0
> implementation?