cppcms-users

Re: [Cppcms-users] Proposal to release CppCMS 2.0 and migrate to C++11

[Artyom B. <art...@gm...>]

On Tue, Nov 1, 2016 at 12:09 PM, Shiv Shankar Dayal
<shi...@gm...> wrote:
> Is there an issue/todo list which is remaining in 1.2.0.0 release? I can
> find sometime and hack a bit of code if others are willing to review it.

Yes: http://cppcms.com/wikipp/en/page/cppcms_1x_tasks#CppCMS.1.1.0.-.Next.Release

The plugin stuff is almost complete mostly pending documentation.

For the session-integration - there were recent changes in the API and
rework needed for PHP, Asp.Net, Java and Python modules to reflect
updated API. Also what is MOST important is to write a standard unit
test in Web-Browser JavaScript and implement
it for CppCMS session and preferably for all these 4 modules so when
writing a new module I just can run it as as.

Also virtual hosts are something I want to do for a long time and
don't get to it.

Other than that it is quite ready.

Artyom

Re: [Cppcms-users] Proposal to release CppCMS 2.0 and migrate to C++11

[CN <cn...@fa...>]

On Tue, Nov 1, 2016, at 09:31 PM, Artyom Beilis wrote:
> The plugin stuff is almost complete mostly pending documentation.
> 
> For the session-integration - there were recent changes in the API and
> rework needed for PHP, Asp.Net, Java and Python modules to reflect
> updated API.

I have little knowledge about the new "session-integration" API. My
instinct tells me that I am unlikely to need these features in
foreseeable future.  If my instinct is correct, I am worried about the
size of new CppCMS.

Will there be compiler directives for me to disable these incoming
unwanted features to avoid a bloated CppCMS executable?

Best Regards,
CN

-- 
http://www.fastmail.com - Access all of your messages and folders
                          wherever you are

Re: [Cppcms-users] Proposal to release CppCMS 2.0 and migrate to C++11

[Artyom B. <art...@gm...>]

>> For the session-integration - there were recent changes in the API and
>> rework needed for PHP, Asp.Net, Java and Python modules to reflect
>> updated API.
>
> I have little knowledge about the new "session-integration" API. My
> instinct tells me that I am unlikely to need these features in
> foreseeable future.  If my instinct is correct, I am worried about the
> size of new CppCMS.
>
> Will there be compiler directives for me to disable these incoming
> unwanted features to avoid a bloated CppCMS executable?
>

On the CppCMS side it is barely tiny C wrapper of C++ session functionality.

The "bloat" comes on external project that isn't compiled to CppCMS that load
cppcms so/dll C API.

So it isn't expected to create any significant addition. If you still
want to disable it
you are welcome to write a tiny patch that removes this stuff from
compilation/testing.

Artyom