From: "John E. Bossom" <drifting@pioneerwireless.ca>
To: pthreads-win32@sourceware.org
Subject: RE: strange pthread_create cap
Date: Wed, 02 Sep 2009 23:53:00 -0000 [thread overview]
Message-ID: <20090902195352.b1k55tqsrccggcc8@webmail.pioneerwireless.ca> (raw)
In-Reply-To: <001c01ca2bfb$147ad3a0$3d707ae0$@kindred@swri.org>
If Laura is running on Windows XP... there is a built in limit on the
number of simultaneously openned sockets... This is on purpose...
to prevent you from turning Windows XP into a Server...
Cheers,
John E. Bossom
Quoting robert kindred <robert.kindred@swri.org>:
> Hello, Ross:
>
> [snip]
>>
>> Hi Laura,
>>
> [snip]
>>
>> Also, are you testing on a Windows Server or Windows Workstation? I ask
>> because, IIRC and if my information is not out-of-date, workstations
>> have a limit (10) on the number of sockets that can be listening at the
>> same time.
>
> I thought this was true also, but I have had more than 20 connections to my
> Windows service via its listening sockets on my desktop. This limit is
> apparently only applied to Windows services (file shares, etc.). My .02,
> though I don't think it solves Laura's problem.
>
>>
>> Ross
>>
>> Laura Arhire wrote:
>> > Hello
>> >
>> > I'm having some trouble with pthreads-win and sockets, wondering if
>> > anyone can help. I have a test setup with a loop which iterates a
>> > number of times. Inside the loop, I create a thread on which I run an
>> > SSL server socket. After the thread is created, I connect an SSL
>> > Client socket to the server socket, then disconnect it, disconnect
>> the
>> > server socket, and issue a pthread_join.
>
> [snip]
>
>> >
>> > Thank you in advance,
>> > Laura
>
> Robert Kindred
>
>
next prev parent reply other threads:[~2009-09-02 23:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-02 10:49 Laura Arhire
2009-09-02 14:28 ` Ross Johnson
2009-09-02 14:36 ` Ross Johnson
2009-09-02 18:28 ` robert kindred
2009-09-02 23:53 ` John E. Bossom [this message]
2009-09-03 6:41 ` Laura Arhire
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090902195352.b1k55tqsrccggcc8@webmail.pioneerwireless.ca \
--to=drifting@pioneerwireless.ca \
--cc=pthreads-win32@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).