Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
I should probably clarify, the local application did not close the socket, but neither did the remote application. And yet the socket did close. So I'm trying to figure out where the socket originally closed and from there why the socket closed. -fjr Frank Ramsay Systems Programmer Castel, Inc 100 Cummings Center Suite 157h Beverly, MA 01915 (978) 236 1000 (voice) (978) 236 1197 (fax) Email: framsay at castelhq.com |---------+----------------------------> | | Nathan Meyers | | | <nmeyers at javalinu| | | x.net> | | | Sent by: | | | discuss-admin at blu| | | .org | | | | | | | | | 05/02/2003 09:53 | | | AM | |---------+----------------------------> >------------------------------------------------------------------------------------------------------------------------------| | | | To: FRamsay at castelhq.com | | cc: discuss at blu.org | | Subject: Re: socket closing question | >------------------------------------------------------------------------------------------------------------------------------| On Fri, May 02, 2003 at 09:45:26AM -0400, FRamsay at castelhq.com wrote: > > When a socket closes, is there a way to determine if it closed locally or > remotely? What do you mean by "closed locally"? That your own application closed it? Nathan Meyers nmeyers at javalinux.net > > > -fjr > > > Frank Ramsay > Systems Programmer > Castel, Inc > 100 Cummings Center > Suite 157h > Beverly, MA 01915 > (978) 236 1000 (voice) > (978) 236 1197 (fax) > Email: framsay at castelhq.com _______________________________________________ Discuss mailing list Discuss at blu.org http://www.blu.org/mailman/listinfo/discuss
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |