🚀 go-pugleaf

In article <30794@castle.ed.ac.uk>, ercm20@festival.ed.ac.uk (Sam Wilson)
wrote:
> 
> Since this seems to be independent of the specific application I assume
> it's a MacTCP problem, possibly a shortage of memory.  Unfortunately I
> don't know of any way of configuring memory for MacTCP (presumably it
> uses the System heap) and can only guess that there's a general shortage
> of System memory at the moments when this problem happens.  I'll
> continue to investigate (though the machine is actually 2 miles away
> from my office!) but if anyone has come across this sort of behaviour
> I'd be interested in knowing. 
> 
MacTCP has little to do with the size of window that is advertised to the
remote host.  The application that is using MacTCP gves MacTCP the memory
needed to maintain the connection.  The application program needs to give
MacTCP sufficient memory to maintain the connection.  Application
programers should use the formula provided in the MacTCP Programmer's Guide
to guide them with memory allocation remembering that their software may be
used on links that have a larger datagram size than Ethernet.  Programmers
should factor the data link MTU  in their memory calculations.

John Veizades...
MacTCP Lead Engineer
Apple Computer, Inc.