Re: [Cppcms-users] feedback after testing cppcms svn trunk compiled with msvc2005

[Artyom <art...@ya...>]

Hello,

I've committed infinite loop and urandom patches.
- the backtrace patch, no needed to do it the way you did
  as I already has support of older SDK. Just changed ifdef
  check if it works
- Apache/win32 shutdown support added as well, pleas check this.

Artyom




----- Original Message ----
> From: Cristian Oneț <one...@gm...>
> To: cpp...@li...
> Sent: Thu, January 20, 2011 12:37:32 PM
> Subject: [Cppcms-users] feedback after testing cppcms svn trunk compiled with 
>msvc2005
> 
> Hi,
> 
> I'm currently testing cppcms from svn trunk compiled with msvc2005  (I
> know that the wiki states that only MSVC9 and MSVC10 are supported  but
> MSVC8 works just as fine).
> As a first impression I would like to say  that the lib looks really
> good. I intend to use it in combination with  apache+mod_fastcgi.
> After a few days of working with it I found the following  issues and I
> want to share them with you:
> 1. The application does not  handle shutdown requests sent by
> mod_fastcgi; a simple solution would be to  add the mechanism used in
> libfcgi (the fastcgi client implementation provided  by
> www.fastcgi.com) see  the attached
> apache_mod_fastcgi_nice_shutdown.patch - nothe that the  implementation
> could be improved to use a cppcms thread instead of  _beginthread.
> 2. When trying the hello/form example I was getting an infinite  loop
> in the application due to the fact that an input stream was  tested
> only for eof and not for validity  see
> http_request_infinite_loop.patch.
> These two where critical issues that  I would like to see solved
> somehow in cppcms. The following two patches are  just insignificant
> improvements:
> 3. Enable using external boost lib while  running cmake configure and
> add an extra name for the zlib library on  Windows
> cmake_permit_using_external_boost_and_zlib_on_win_name.patch
> 4.  This fixes the only code incompatibility I have found on  msvc2005
> (mscv_2005_compatibility.patch) but googleing revealed that this  can
> be fixed using a never winsdk so this is only important if  upgrading
> is not an option
> This is all for  now.
> 
> Regards,
> Cristian Oneț
>