Re: [cgi-devel] Unix sockets timeline

[Ankur G. <ank...@gm...>]

Hi Darren,

 That sounds good.  Looking forward to seeing the latest changes.

 I had some feedback from testing some of the stuff that's currently there:

i) The echo_threaded example seems to block if the first thread hangs.  Even
though multiple threads are created, it seems to behave like a single
threaded program.

ii) server4 example doesn't seem to compile with boost 1.43

iii) I saw the following error in serve3 example after adding a delay in
handle_request and sending multiple browser requests.  The error happened
when the delay got over.  Is this an exception that should be caught?

Error system:32: Broken pipe
terminate called after throwing an instance of 'boost::system::system_error'
  what():  Broken pipe
Aborted


Thanks,
-Ankur

On Mon, Jul 26, 2010 at 4:43 PM, Darren Garvey <
lis...@go...> wrote:

> Hi Ankur,
>
>
> On 26 July 2010 07:02, Ankur Gupta <ank...@gm...> wrote:
>
>>  Is there any timeline for Unix domain sockets implementation?  This
>> should help performance quite a bit I feel.
>>
>
> I have been making a large chunk of changes locally, none of which are in
> the repository quite yet.
>
> These changes include support for TCP sockets on Windows (ie. for external
> FastCGI) and for Unix sockets, both of which are compile-time choices. There
> is also an experimental dynamic wrapper over the main classes of the
> library, which allows for protocol and / or connection type to be picked at
> runtime.
>
> I will try and find time to commit these in the next couple of weeks.
> Especially with the dynamic CGI stuff, I'm still a bit unsure about the
> naming conventions, async functionality and a couple of other details so
> it'd be interesting to see what other's thoughts were.
>
> Cheers,
> Darren
>