Re: macnetworkprog digest, Vol 3 #711 - 3 msgs
Re: macnetworkprog digest, Vol 3 #711 - 3 msgs
- Subject: Re: macnetworkprog digest, Vol 3 #711 - 3 msgs
- From: Dakidd <email@hidden>
- Date: Wed, 28 Apr 2004 09:51:09 -0700
>
Please don't cross post between lists. When folks on the other list
>
do a "reply to all", they get bounced because they're not subscribed
>
to MacNetworkProg. No big deal, but something to keep in mind in the
>
future.
Ahhh... Wasn't aware that was/could be a difficulty. Something I hadn't
considered *AT ALL*, definitely. Won't happen again.
>
At 8:34 -0700 27/4/04, Dakidd wrote:
>
>Anybody able to point me at what I'm apparently missing?
>
>
"OpenTransport.h" (-:
>
>
> ECONNREFUSED = 61, /* Connection refused */
>
>
It is actually documented, you just have to work out that
>
kECONNREFUSEDErr (-3260) is the OSStatus range mapping of
>
ECONNREFUSED (61) via the OSStatus2E and E2OSStatus macros.
>
>
The positive version of this error code (kECONNREFUSED) is
>
returned by Open Transport as a reason code in a disconnect
>
message, indicating that the other side refused the connection.
>
-- <http://developer.apple.com/documentation/mac/NetworkingOT/
>
NetworkingWOT-479.html>
>
>
Of course, by the time you know enough about OT to understand this
>
comment and find it in the 886 page document, you no longer need the
>
help )-:
Precisely...
Side note:
That comment is *WRONG*. What comes back in the "reason" field of my
TDiscon struct is the raw 61, not the "translated" version. Or are we
"talking around each other" again due to my not understanding the docs and
their clear-as-mud wording?
>
So, yes, I know that this is non-obvious and very hard to find in the
>
documentation. I apologise for that, both on behalf of Apple and
>
personally (I was the primary reviewer on the book).
>
However, it's unlikely to get fixed because OT is now officially
>
deprecated, so we're not updating the documentation. We recommend
>
that you avoid the OT API unless you have to support pre-X systems.
Excuse me while I go off on a minor rant for a moment...
Yeah... Same old song - "You're not using the latest/greatest/newest
hardware/software, so suffer". I'm using a 7500 (Jacked up to a G4/350)
with 9.1. I can't figure out a way to justifiy spending the $$ on (1) A New
computer (There's nothing wrong with THIS one!) (2) MacOS X and its "Buy a
new copy every six months as we work the bugs out of it by selling the
customers a new installment of beta-ware and wait for them to scream bloody
murder about the bugs before repeating the cycle" update model.
But I can and do still want to code for the Macintosh. So let's climb the
learning-curve of Carbon, and try to make do with what's available there.
(You have *NO* concept how badly I wish there was a "Sockets" type
networking interface on the Mac - No disrespect to Mathias, but GUSI don't
cut it - Been there, done that, abandoned the idea as entirely unworkable)
Y'know, there used to be a time when Apple Inc actually *WANTED* to hold
onto the legacy folks. Even if it was only to avoid pissing them off enough
to push them into buying a Wintel box next time around. Now, unless you're
cooking up a project for the G6 (Yes, I know it hasn't even shown up on the
edge of the radar yet. That's my entire point - unless you're coding for a
machine that might never exist, rather than the one sitting on your desk
right now, you've got no support from Apple.), and planning to target a
3-years-til-first-beta-release OS while doing it, the brand loyalty you've
shown over the year is repaid with "That's officially unsupported, so
you're on your own. But if you buy this nice, expensive new machine (and
the software that doesn't officially exist yet) We can help you". Bah...
Not all of us have a budget that permits staying on "the bleeding edge",
even if we had a desire to try. Sorry, Quinn - I've long admired your
contributions to the Mac networking world, but the networking docs that
come out of Cupertino have consistently been the absolute worst
documentation it has ever been my misfortune to have to deal with - Poor
layout, lousy information, and nearly worhtless unless/until you've got
every page memorized letter-perfect, then spent a year or so of "finding
the pitfalls" on your own :( The OpenTransport docs have always been the
worst, despite that being one of the (potentially...) nicest bits of
technology Apple has ever turned out.
Sorry if it sounds over-dramatic, Quinn, but as an Apple
user/programmer/fan since the days of the Apple ][, this (in general, not
this issue/your response in particular) is the kind of treatment I'd expect
from Microsoft, not Apple.
>
On a related note, if you are working with OT, please make sure to
>
use the "Inside Macintosh: Networking with Open Transport" version
>
1.3 document as your primary reference.
>
>
<http://developer.apple.com/documentation/mac/pdf/NetworkingOT.pdf>
That would be the one I'm working with, I'm pretty sure. - First page, at
the bottom, is tagged "Revised for version 1.3, November 1997", showing an
Apple Copyright range of 1994-1997. If that's not the right one, let me
know.
>
The Carbon documentation has a couple of useful updates, but it also
>
omits some key information (such as the comment quoted above).
Aside from documenting the "...InContext" changes, and the "loss" of almost
everything but TCP/IP and AppleTalk, I'm not seeing a lot of significant
change going on between the two versions.
Don Bruder - email@hidden <--- Preferred Email - unmunged
I will choose a path that's clear: I will choose Free Will! - N. Peart
_______________________________________________
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.