| To: | "REALbasic Betas" <realbasic-betas at lists dot realsoftware dot com> |
|---|---|
| Subject: | Re: only 1 TCPsocket connection at a time? |
| From: | Aliacta <rb at aliacta dot com> |
| Date: | Thu, 1 Apr 2004 03:17:16 +0200 |
| References: | <a06020406bc8dcaff5a7b at [192 dot 168 dot 0 dot 101]> <a06020409bc8dd094a971 at [192 dot 168 dot 0 dot 101]> <a0602040cbc8ddb031b38 at [192 dot 168 dot 0 dot 101]> <a06020402bc9100969e01 at [192 dot 168 dot 0 dot 101]> <042c01c41778$3fea98b0$f10a0a0a at Circe> <a06020403bc91125363b3 at [192 dot 168 dot 0 dot 101]> <002601c41782$68ebfce0$6400a8c0 at Circe> <a06020404bc911a6c4998 at [192 dot 168 dot 0 dot 101]> |
> These are 2 client sockets, they're not listening. The server towhich they connect isn't made with RB.Once one of them connects, that port is busy. That is why the second socket cannot connect and reports an error. It's expected results, not a bug. Is this only 1 socket per window or only 1 per application? If it'd be per window then I could live with it. The serversocket is no solution because it can only listen, isn't it? Marc - - - Unsubscribe or switch delivery mode: <http://support.realsoftware.com/listmanager/> Search the archives of this list here: <http://support.realsoftware.com/listarchives/lists.html> |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: only 1 TCPsocket connection at a time?, Aliacta |
|---|---|
| Next by Date: | Re: only 1 TCPsocket connection at a time?, Chris Willis |
| Previous by Thread: | Re: only 1 TCPsocket connection at a time?, Aliacta |
| Next by Thread: | Re: only 1 TCPsocket connection at a time?, Chris Willis |
| Indexes: | [Date] [Thread] [Top] [All Lists] |