baaa01@mixcom.UUCP (Merge Technologies Inc.) (10/21/90)
My employer has received a request to port our
TCP/IP application software to a Mac. However, we have
no Mac software development or Mac TCP/IP experience.
We have lots of UNIX & MS-DOS TCP/IP experience, though.
(Dev language = C.)
We can get a consultant to help set up a Mac for software
development, so that is not a problem. But we have not found
someone with Mac TCP/IP applications experience.
Questions I have (that the net can answer, I hope):
The TCP/IP software uses the "std."
BSD socket interface to TCP/IP. It has been
ported to several UNIX platforms and two
MS-DOS TCP/IP packages. Does Mac TCP/IP for Mac OS
use "std." BSD socket interface? What about a
select() function? (Can non-blocking I/O be done
easily using the select() function as it should
be used?)
Are there considerations for applications when
an application runs with MultiFinder? In other
words, do I have to be concerned about making the
application share the CPU to prevent timeouts from
occurring in the communications software, or does
MultiFinder provide "equal" CPU sharing something
like DesqView does with MS-DOS? (The software works
find with an MS-DOS multitasker.)
Thank you for your help.
Dean
--
Merge Technologies Inc. P.O. BOX 27366 Milwaukee, WI 53227
==========(414) 256-5360========================merge@mixcom.UUCP=============
Diagnostic Medical Image Communications Products