Re: [Cppcms-users] CppCMS 1.1 - Progress Report

[Christian G. <chr...@gm...>]

Hi

2015-12-26 20:12 GMT+01:00 Artyom Beilis <art...@gm...>:
> Hello Dear CppCMS  Users,
>
> If someone getting this as duplicate my apologize.
> (Apparently GMail does not like my Yahoo mail sent via mailman :-)  )
>
> --------------------
>
> I'm getting ready to release next CppCMS beta version 1.1 (that would
> become stable as 1.2)
>

Great to hear!

> Some preview of the work that was done so far:
>
>   http://cppcms.com/wikipp/en/page/cppcms_1_2_whats_new
>
> In the nutshell
>
> - Redesigned applications pool and its API.
> - New non-blocking I/O mode for asynchronous applications.
> - On-the-fly uploads/post content processing support.
> - Independent of context use of cache and session interfaces
> - Support of non-cookies based session handling
> - Integration of session handling with 3rd part technologies:
>   PHP, Java Servlet, Aps.Net and so on and contributed modules.
>   http://blog.cppcms.com/post/117
> - Major performance and memory use improvements.
> - Headers and Source separation by templates compiler.
>   (Special thanks to Lee Elenbaas for the major contribution)
>
> There are still few relatively small tasks in the TODO list before
> beta will be officially ready.
>
>   http://cppcms.com/wikipp/en/page/cppcms_1x_tasks#CppCMS.1.1.0.-.Next.Release
>
> More than that  I'm changing the release policy to something that I
> should do for a looooong time ago:
>
>   --- release early, release often ---
>

Superb!

> CppCMS 1.1 was for too long in development and it isn't good...
>
> I want you guys to looking on it:
>
> - Try to build the version from trunk
> - Try new API and report your impressions.
> - Ask questions.
>
> If some API issues are discovered I can make API changes before 1.2 is out.
> However once 1.2 is released... the API will be frozen.
>

In my big cppcms based application I have a custom session_storage and
run into the problem
that I need to access a shared resource (singleton class) of the
process in the loaded so/dll.
To solve this I made use of shared-memory to store the address of that
shared object and access
that information in my session_storage.

Maybe there is a good way to extend the API to be able to pass a void
pointer to shared_pool, extend
the sessions_generator entry point and pass the custom void pointer to
the entry_point.

What is the deadline for the API freeze. I can come up with an RFC
patch for discussion.

greets
--
Christian Gmeiner, MSc

https://soundcloud.com/christian-gmeiner