Re: Socket connection return "Process file table overflow."
- From: Nuno <nuno.esculcas@xxxxxxxxx>
- Date: Tue, 25 Mar 2008 10:02:35 -0700 (PDT)
Hi,
I think i do not look for any specification, because i only need to
implement a simple file download from a HTTPS Server...
Can you give me some guidelines of what is needed to open a connection
and to close, or to prepare it to the next download...
Thanks
On 25 Mar, 16:55, David Schwartz <dav...@xxxxxxxxxxxxx> wrote:
On Mar 25, 9:19 am, Nuno <nuno.escul...@xxxxxxxxx> wrote:
For your first question, i don't know how to respond, how i see this?
i implement by examples that i find in the internet...
That's a huge mistake. You should implement the protocol from the
specification. Otherwise, you have no idea what the server is allowed
to do.
I think the problem is on my closing connections function too, but
where i can't seem to understand, I'm freeing the context because the
idea is to free/release/close everything that i opened... i should not
be freeing the context?
There is no reason to free the context if you still need it, which you
do.
DS
.
- Follow-Ups:
- Re: Socket connection return "Process file table overflow."
- From: David Schwartz
- Re: Socket connection return "Process file table overflow."
- References:
- Socket connection return "Process file table overflow."
- From: Nuno
- Re: Socket connection return "Process file table overflow."
- From: David Schwartz
- Re: Socket connection return "Process file table overflow."
- From: Nuno
- Re: Socket connection return "Process file table overflow."
- From: David Schwartz
- Socket connection return "Process file table overflow."
- Prev by Date: Re: Socket connection return "Process file table overflow."
- Next by Date: Re: Socket connection return "Process file table overflow."
- Previous by thread: Re: Socket connection return "Process file table overflow."
- Next by thread: Re: Socket connection return "Process file table overflow."
- Index(es):
Relevant Pages
|