Re: Listening on the port
Re: Listening on the port
- Subject: Re: Listening on the port
- From: Igor garnov <email@hidden>
- Date: Sat, 8 May 2004 15:04:17 +0400
On Saturday, May 8, 2004, at 14:22 Europe/Moscow, Quinn wrote:
So, on Mac OS 9 and Classic mode on Mac OS X, am I entitled to bind
to port 137?
Yes. Classic applications get access to low-numbered ports, but
non-Classic applications don't. Don't ask me to justify this decision
or I'll start to whimper (-;
"Classic applications" - do these include Carbon CFM applications?
But my CFM app checks if it's launched in Mac OS X or 9. If it feels
it's running on 9, it tries to bind to port 137 to listen to
broadcasts.
What do you do if you're run on Mac OS X?
Well, I plan to make use of Network Services Location Manager.
I want to display the windows network neighborhood. Apparently, if I do
it on my own (and this is the case on Mac OS 9), I will have to listen
to the port 137. On Mac OS X it is not worth disturbing a user with
authentication procedure - if it's possible I would like to use the
aforementioned Network Services.
This is not a major feature of the application, so I can sacrifice it
for Mac OS X users, especially taking into account that they can access
the Network Neighborhood via the Finder.
And, I still wonder - is there some difference between binding to a
port to listen to unicast datagrams and broadcast datagrams? I am now
just binding the endpoint to the port 137. This endpoint was created
using UDP configuration. So, I take it now I am listening to ALL
incoming datagrams sent to port 137 - both broadcast and unicast. Is
this correct?
Regards,
Igor
_______________________________________________
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.