On Sun, Nov 29, 2009 at 8:33 PM, Nick Arnett <nick.arn...@gmail.com> wrote:
> On Sun, Nov 29, 2009 at 4:01 PM, Steve Holden <holden...@gmail.com> wrote: > > >> >>> Not at all. The client will typically use an "ephemeral" port (one it >> obtains by saying to its local TCP layer "gimme a port number, I don't care >> what it is"). The connection (any connection) has *two* endpoints, and the >> port numbers each system uses are up to that system. >> >> Obviously you want the server to listen on a "well-known" port most of the >> time, though as you have observed the Django administrator can configure the >> server to listen on any desired port. But the client really doesn't care - >> it just expects the server to reply to the same port number it sent its >> request from. >> > > Of course, but I can't imagine why anybody would ever worry about that at > the application level. > > Me neither. The server just replies on the socket that the message comes in on. I'd like to know why the OP felt it was important to be able to identify the remote port. regards Steve -- Steve Holden +1 571 484 6266 +1 800 494 3119 Holden Web LLC http://www.holdenweb.com/ -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
