[wsf-c-dev] Issues for a next generation C stack

[Damitha Kumarage]

>- Evolution vs revolution.  How do we get from where we are today to
>where we want to be eventually?  Do we gradually evolve the current
>code-base or do we start a new code-base?  The technical viability of an
>evolutionary approach will obviously depend to some extent on the
>answers to the above questions.
>
>
>  
>

Frankly I prefer to write the new Stack in C++ at least for it's advantage on OO(restricted)
and memory handling. But I think that's a decision we should have taken when we started in the first
place one year back. When I weigh the pros and cons I think we should be better with the
evolution(in my opinion). I have the following points to strengthen my argument.

* Comunity interest on the project has just started to grow. 

* Not having exeception handling and stl means we again have to do lot of work on our own. 
  Can we take our existing utils library to the next stack with improvements like
  memeoy and thread pools?. Regarding the error handling again we are in the same place.

* Doing the same thing again(in different language/design) would restrict us on exploring new boundaries.
 
* Is the main advantage we get by using C++ is visible to the users using our core? As I understand it is not
  so. using OO or using destructors is not the users concern. What he needs is a stable api 
  and a robust implementation. With the evolution we can achieve this by introducing memory pools, removing 
  macros, removing unneccessary OO and other improvements we have discussed so far.

Damitha



>_______________________________________________
>Wsf-c-dev mailing list
>Wsf-c-dev at wso2.org
>http://wso2.org/cgi-bin/mailman/listinfo/wsf-c-dev
>
>  
>