Mailing-List: contact axis-c-user-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache AXIS C User List" <axis-c-user@ws.apache.org>
Received-SPF: pass (hermes.apache.org: local policy)
In-Reply-To: <20040930101027.74187.qmail@web40613.mail.yahoo.com>
Subject: Re: C and C++ support
Cc: axis-c-dev@ws.apache.org,
        Apache AXIS C User List <axis-c-user@ws.apache.org>
Message-ID: 
 <OF6BA3C3F3.CCC0EE37-ON80256F1F.003D43A2-80256F1F.003D5669@uk.ibm.com>
From: John Hawkins <HAWKINSJ@uk.ibm.com>
Date: Thu, 30 Sep 2004 12:09:58 +0100
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII


Yep - we thought of that already :-)

We're going to set up some server tests to ensure that we don't screw it
up.


John Hawkins


             Samisa Abeysinghe                                             
             <samisa_abeysingh                                             
             e@yahoo.com>                                               To 
                                       Apache AXIS C User List             
             30/09/2004 11:10          <axis-c-user@ws.apache.org>,        
                                       axis-c-dev@ws.apache.org            
                                                                        cc 
             Please respond to                                             
              "Apache AXIS C                                       Subject 
             Developers List"          Re: C and C++ support               
                                                                           
                                                                           
Hi All,
   One of the possible problems of converting the engine to pure C++ is
that, one would have to
keep an eye on both the client side as well as the server side, while the
refactoring is going on.
So it would be necessary to have both client side as well as server side
test cases in place
before we start on this task. (a typical refactoring scenario) I think we
can manage with whatever
tests we have at the moment.
   As long as we keep on testing client and server in parallel, we would be
able to achieve
success with this task.

Thanks,
Samisa...

--- John Hawkins <HAWKINSJ@uk.ibm.com> wrote:

>
>
>
>
> Hi Folks,
>
> Throughout the last year we have come across many problems related to our
> continued commitment to supporting both C and C++ stubs. The design of
the
> engine code has been greatly affected by this and has caused quite a few
> problems particularly with regard to memory management. Please see here
> http://marc.theaimsgroup.com/?l=axis-c-dev&m=109461822722177&w=2 and here
> http://nagoya.apache.org/jira/browse/AXISCPP-149 for some of the issues
we
> have recently uncovered.
>
> The reasoning behind supporting C is clear - to support legacy
> applications. We have had the debate about using C internally for
> performance reasons and I think we have concluded that we need to get the
> code stable and then consider performance. The intermingling of C and C++
> in the core code has created more problems than it would appear to have
> solved (Current performance charts show azis C looking very bad).
>
> In order to improve and stabilise the code I would like to propose that
we
> remove C structures, memory allocation etc. such that we have a 100% C++
> engine. If we did this we can then enhance WSDL2WS such that it creates C
> wrappers for the pure C++ code. There is, in my opinion,  no question
that
> this will improve the quality of the code - particularly memory
management.
>
> If this is agreed upon then I would like to propose that we take a two
> staged approach in the management of this change. I would like us to
> withdraw C support for the NEXT RELEASE ONLY (1.4). In 1.4 we can work on
> making the engine 100% C++. I would then like us to reintroduce the C
> support in the post 1.4 timeframe (1.5) by making the changes to WSDL2WS.
>
> This approach enables us to concentrate on improving the core engine code
> in the first instance without worrying about updating the C support in
> WSDL2WS - code that will get changed in the next release. Once we have
> proven that we have a stable 100% C++ engine we can then concentrate
> entirely on C support - i.e. by producing the nicely encapsulated
> wrappering layer.
>
>
> I hope that we, as a community, can work through this problem quickly so
> that we can make the core code more stable and C support of a much higher
> quality. I look forward to your responses.
>
> (This is copied to both the dev and user community for response.)
>
>
> John.
>
>
>
>
> John Hawkins
>
>
>
>


_______________________________
Do you Yahoo!?
Declare Yourself - Register online to vote today!
http://vote.yahoo.com