Re: OpenTransport problem on OS9.2.2
Re: OpenTransport problem on OS9.2.2
- Subject: Re: OpenTransport problem on OS9.2.2
- From: Alice Hartley <email@hidden>
- Date: Tue, 15 Apr 2003 17:07:16 -0400
>
Hi Alice,
>
>
Your description is very vague, and its especially light on detail
>
about *how* you are using Open Transport. I can certainly imagine
>
seeing the problem you describe if you are using OT endpoints with
>
notifiers.
Yes I know the description is vague.
We do use endpoints and a notifier. The notifier is in our
OpenTransportSupport library which has been unchanged since 1999.
There is also a version of our application which is
InterfaceLib based. With that version of the application
everything works fine. (Using the same OT support library).
So in summary:
InterfaceLib - OS9: OK
CarbonLib - OS9: Bad
OSX: OK.
Is there a difference between InterfaceLib and CarbonLib
handling of OT?
There is a layer above the OT Support library that is written
in Lisp. Is it likely the problem is in the notifier or might
it be in the higher level layer.
>
>
In my experience notifiers seem to behave very differently under OS X
>
vs. under OS 9, where OS X is much more tolerant of design flaws than
>
OS 9. Notifiers really do run at deferred task time on OS 9 which means
>
there are very few safe OS calls, interrupts are very common, and you
>
must be prepared to deal with many more types of errors or odd
>
situations including a short-term lack of memory.
A user with a T1 line has occasionallu seen a lack of memory - NewPtr fails
in the Lisp layer. Newptr is used when OTAllocMem fails.
On the other hand, OS
>
X runs your code at "regular" task time (like the rest of your
>
application) which masks many of these issues.
>
>
Consult the archives, there are plenty of good suggestions about
>
debugging notifiers, especially under OS 9.
>
>
Good luck,
>
Bob Cook
>
>
On Monday, April 14, 2003, at 05:57 PM, Alice Hartley wrote:
>
>
> Our application uses an OpenTransportSupport CFM library of
>
> our creation. The application is CarbonLib based.
>
> Atop that library is some Lisp code that interfaces to
>
> OpenTransport.
>
> Here is the problem.
>
>
>
> (setf stream (open-tcp-stream "www.apple.com" 80))
>
>
>
> (progn (telnet-write-line stream "GET / HTTP/1.0")
>
> (telnet-write-line stream "")
>
> (dotimes (x 10) (print (telnet-read-line stream))))
>
>
>
> With the above code things work fine on either OS9.2.2 or
>
> on OSX 10.2 or greater if the network connection is a modem
>
> (i.e. slow). However if the network connection is
>
> on a T1 line (through ethernet or airport) or cable modem, it fails
>
> on OS9.2.2 but works on OSX 10.2.
>
> The failure may be garbage returned after about 6000 characters
>
> or sometimes a lisp error or sometimes a crash.
>
>
>
> What differences between the OS9 carbonLib implementation
>
> and the OSX implementation might be implicated in this
>
> problem?
>
>
>
> I know the info is rather vague, but I'm hoping.
>
> Thanks for any help.
>
> Alice
>
> _______________________________________________
>
> macnetworkprog mailing list | email@hidden
>
> Help/Unsubscribe/Archives:
>
> http://www.lists.apple.com/mailman/listinfo/macnetworkprog
>
> Do not post admin requests to the list. They will be ignored.
>
_______________________________________________
>
macnetworkprog mailing list | email@hidden
>
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/macnetworkprog
>
Do not post admin requests to the list. They will be ignored.
_______________________________________________
macnetworkprog mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/macnetworkprog
Do not post admin requests to the list. They will be ignored.