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

[nandika at wso2.com]

I think before we actually decide on whether to do evolution or revolution
we should do the possible obvious improvment of Droping unncessary OO types
and macros in the existing code base.
(I think more than 60% of the code can be changed to use opeque structures
instead of OO types which will substancially reduce the memory usage and
improve performance. It is possible to do the change within 2 weeks
considering some of the changes that were done in the past.)

Even if we were to give up the existing code base, this will be great for
who ever that is going to use the code.
(It is a possibility that we may actually have a community who will
maintain the code outside of wso2 by another year)

1. Then measure performance, memory usage etc and compare the results with
existing other soap stacks such as gSOAP , Axis C++, Axis2 Java ,Xfire etc.
If the numbers are bad that means definite need for rewriting but if they
are good, the best option would be the evolutionary path.

2. It is always better to have solid facts in numbers on why we should
drop the existing stuff, if we are to do so.

3. Measuring preformence will reveal the real bottle necks of the existing
code ,which we should take care to avoid if we are to redo the code.

Thanks
Nandika


>>
>> * 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.
>
> These are good points.
>
> The point of using C++ would be to allow us to write better quality
> software faster.  An alternative way to allow us to write better quality
> software faster is to improve the way we do things in C (because I think
> we would all agree that our current way of doing things is painful).  So
> before we can answer the C vs C++ question, I think we have to look in
> more detail at the possibilities for improving our C infrastructure,
> particularly in the areas of memory management and error handling.
>
> James
>
>
>
> _______________________________________________
> Wsf-c-dev mailing list
> Wsf-c-dev at wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/wsf-c-dev
>