s" in the
> broader
> > > > sense of the term meaning anyone who wants to write code to work
> with
> > > > Axis). I know of quite a few people who write their own servlets,
> > > > providers and transports - I believe you're talking about
s). I know of quite a few people who write their own servlets,
> > > providers and transports - I believe you're talking about changing
> > _their_
> > > interfaces.
> > > -Dug
> >
> > >
> > > James M Snell/Fresno/IBM@IBMUS on 10/25/2002
who write their own servlets,
> > providers and transports - I believe you're talking about changing
> _their_
> > interfaces.
> > -Dug
>
> >
> > James M Snell/Fresno/IBM@IBMUS on 10/25/2002 11:39:15 AM
>
> > Please respond to [EMAIL PROTECTED]
>
&
Wrappers supporting old interfaces is good :-)
-Dug
James M Snell/Fresno/IBM@IBMUS on 10/25/2002 12:13:48 PM
Please respond to [EMAIL PROTECTED]
To:[EMAIL PROTECTED]
cc:
Subject:Re: [IMPORTANT!] Proposed Axis Async Development Plan
Possible interim solution: one of the utility
M Snell/Fresno/IBM@IBMUS on 10/25/2002 11:39:15 AM
> Please respond to [EMAIL PROTECTED]
> To: [EMAIL PROTECTED]
> cc:
> Subject:Re: [IMPORTANT!] Proposed Axis Async Development Plan
>
> The proposed changes ARE internal to Axis. They change the interfaces
to
> the
hanging _their_
interfaces.
-Dug
James M Snell/Fresno/IBM@IBMUS on 10/25/2002 11:39:15 AM
Please respond to [EMAIL PROTECTED]
To:[EMAIL PROTECTED]
cc:
Subject: Re: [IMPORTANT!] Proposed Axis Async Development Plan
The proposed changes ARE internal to Axis. They change the interfaces to
the AxisE
cc
bcc
Subject
Re: [IMPORTANT!] Proposed Axis Async Development Plan
In some of your notes you've stated that the new messaging pattern you
want
to do is strictly internal and yet this note would seem to imply
otherwise.
Now that 1.0 has shipped we all know that we must be very ca
few very simple concepts: Handlers
and Chains (that's what I see anyway) - and it would be a shame if we lost
that. So, please it simple.
-Dug
James M Snell/Fresno/IBM@IBMUS on 10/23/2002 07:04:29 PM
Please respond to [EMAIL PROTECTED]
To:[EMAIL PROTECTED]
cc:
Subject:[IMPORTANT!] P
@;us.ibm.com]
Sent: Wednesday, October 23, 2002 7:04 PM
To: [EMAIL PROTECTED]
Subject: [IMPORTANT!] Proposed Axis Async Development Plan
On the phone call today, we discussed the fact that the Internal Message
Exchange proposal represents a significant change to the Axis internals
and should ide
resno/IBM@IBMUS
10/23/2002 04:04 PM
Please respond to axis-dev
To
[EMAIL PROTECTED]
cc
bcc
Subject
[IMPORTANT!] Proposed Axis Async Development Plan
On the phone call today, we discussed the fact that the Internal Message
Exchange proposal represents a significant change to the Axis internals
On the phone call today, we discussed the fact that the Internal Message
Exchange proposal represents a significant change to the Axis internals
and should ideally be broken up so that it can be incrementally
introduced into the code. Here's my proposal for how to break up the
work.
Phase 1:
11 matches
Mail list logo
