I agree as well. +1 to JMS, -1 to new API's.

thanks,
dims

--- Glyn Normington <[EMAIL PROTECTED]> wrote:
> I agree with Glen.
> 
> Glyn
> 
> 
>                                                                                      
>           
>                                     
>                       Glen Daniels                                                   
>           
>                                     
>                       <gdaniels@macrome        To:       "'[EMAIL PROTECTED]'"
> <[EMAIL PROTECTED]>                       
>                       dia.com>                 cc:                                   
>           
>                                     
>                                                Subject:  RE: Commiting the Sonic JMS 
>and my
> async mods to main source                
>                       09/16/02 08:26 PM                                              
>           
>                                     
>                       Please respond to                                              
>           
>                                     
>                       axis-dev                                                       
>           
>                                     
>                                                                                      
>           
>                                     
>                                                                                      
>           
>                                     
> 
> 
> 
> 
> Hi folks!
> 
> Here's my take on this for 1.0:
> 
>    JMS transport     +1
> 
> A new transport doesn't change anything, and adds functionality.
> 
>    New APIs          -1
> 
> The reason I'm -1 to the new APIs, despite their "provisional" nature is
> that I don't want to make any promises about supporting or continuing
> forward with a set of APIs that have just appeared a week before release (I
> think putting them in, even with disclaimers, implies something).  I know
> they don't affect the tests or the other APIs, but they are brand new and
> we haven't discussed them thoroughly or tested them yet.  I'd really prefer
> we waited until after 1.0 to introduce any kind of "true async" API.
> Sorry, James, no offense - I'm sure the design is fine, I just don't feel
> like we have time to agree on that as a group before 1.0.  It should still
> be easy to unzip a file over a 1.0 distribution to try this stuff out if
> desired....
> 
> This is my gut feeling, but I'm willing to reconsider if there is broad
> agreement from the rest of the team that it's a good idea.
> 
> --Glen
> 
> > -----Original Message-----
> > From: James M Snell [mailto:[EMAIL PROTECTED]]
> > Sent: Monday, September 16, 2002 2:02 PM
> > To: [EMAIL PROTECTED]
> > Subject: Fw: Commiting the Sonic JMS and my async mods to main source
> >
> >
> > Trying this again.. for some reason the original was rejected.
> >
> > - James Snell
> >      IBM Emerging Technologies
> >      [EMAIL PROTECTED]
> >      (559) 587-1233 (office)
> >      (700) 544-9035 (t/l)
> >      Programming Web Services With SOAP
> >          O'Reilly & Associates, ISBN 0596000952
> >
> >      Have I not commanded you? Be strong and courageous.
> >      Do not be terrified, do not be discouraged, for the Lord your
> >      God will be with you whereever you go.    - Joshua 1:9
> > ----- Forwarded by James M Snell/Fresno/IBM on 09/16/2002
> > 11:01 AM -----
> >
> > James M Snell/Fresno/IBM
> > 09/16/2002 08:49 AM
> >
> > To
> > [EMAIL PROTECTED]
> > cc
> >
> > bcc
> >
> > Subject
> > Commiting the Sonic JMS and my async mods to main source
> >
> >
> > Ok... after talking with the Sonic folks we've come to the
> > conclusion that
> > 1) my proposed async mods to the Axis Call object and their
> > proposed JMS
> > transport do not conflict with one another, 2) are capable of working
> > together and (most importantly) 3) can be merged into the
> > main Axis source
> > tree without breaking any of the existing Axis
> > functional-tests, samples,
> > TCK compliance, etc etc.
> >
> > After talking it over with Sam, I'd like to go ahead and
> > commit the two
> > proposals into the main source pre-1.0 as "provisional features".  In
> > other words, they are a provide a preview of functionality
> > that will be
> > evolved to a more fully developed state later.  The
> > documentation will
> > warn users that these features should not be used for production
> > environments since most likely they details of the API or transport
> > config, etc will change with subsequent versions.  The
> > benefit to Axis is
> > that 1) it doesn't interfere with anything else in Axis and
> > 2) it adds new
> > functionality that previously didn't exist.
> >
> > I know that some of you have reservations about checking in new stuff
> > before the 1.0 release but we've taken pains to verify that
> > everything
> > still builds, still works, etc and don't see a problem
> > checking it in.
> > Given that, if I don't hear any -1's before tomorrow
> > (Tuesday) morning,
> > I'm going to go ahead and check it in.
> >
> > (I'm ducking now)
> >
> > - James Snell
> >      IBM Emerging Technologies
> >      [EMAIL PROTECTED]
> >      (559) 587-1233 (office)
> >      (700) 544-9035 (t/l)
> >      Programming Web Services With SOAP
> >          O'Reilly & Associates, ISBN 0596000952
> >
> >      Have I not commanded you? Be strong and courageous.
> >      Do not be terrified, do not be discouraged, for the Lord your
> >      God will be with you whereever you go.    - Joshua 1:9
> >
> 
> 
> 
> 


=====
Davanum Srinivas - http://xml.apache.org/~dims/

__________________________________________________
Do you Yahoo!?
Yahoo! News - Today's headlines
http://news.yahoo.com

Reply via email to