soaplite-devel

[Soaplite-devel] State of the SOAP

[Robert L. <rla...@ao...>]

I just read the State of the SOAP post on soaplite.com.  I couldn't 
agree more.  It's pretty awful code, and slogging through it to figure 
out why it's doing something wrong is way too cumbersome.

I just discovered an ugly little bug today with how WSDLs are converted 
into code, and how parameter handling is (to be blunt) broken.  The fix 
however, is even uglier.

If work on a rewrite is underway, I'm interested in contributing.

Rob

Re: [Soaplite-devel] State of the SOAP

[Charlie B. <cha...@gm...>]

I think a lot of people are wanting to help, I know I am.  What we need is a
little leadership to help get the ball rolling.

On 2/16/07, Robert Landrum < rla...@ao...> wrote:
>
> I just read the State of the SOAP post on soaplite.com.  I couldn't
> agree more.  It's pretty awful code, and slogging through it to figure
> out why it's doing something wrong is way too cumbersome.
>
> I just discovered an ugly little bug today with how WSDLs are converted
> into code, and how parameter handling is (to be blunt) broken.  The fix
> however, is even uglier.
>
> If work on a rewrite is underway, I'm interested in contributing.
>
> Rob
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share
> your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Soaplite-devel mailing list
> Soa...@li...
> https://lists.sourceforge.net/lists/listinfo/soaplite-devel
>

Re: [Soaplite-devel] State of the SOAP

[Robert L. <rla...@ao...>]

Hmm...  Well...  Maybe the first step should be to determine what 
features people are actually using.  We need to figure out which 
features we can cut out of SOAP, and which features we need to add. 
Once we have that list...

The next step would be an RFC, where we allow for anyone with a good 
idea to submit a proposal, solution, or other recommendation.  In 
general, we would want to see plans for the redevelopment of SOAP::Lite.

With that in hand, we could separate feature requests for structural 
changes, and develop a final draft plan for the layout of the module. 
Community sign off would probably be appreciated.

Once a plan had been decided upon, only then would development commence 
on the module itself.

Rob

Charlie Bowman wrote:
> I think a lot of people are wanting to help, I know I am.  What we need 
> is a little leadership to help get the ball rolling.
> 
> On 2/16/07, *Robert Landrum* < rla...@ao... 
> <mailto:rla...@ao...>> wrote:
> 
>     I just read the State of the SOAP post on soaplite.com
>     <http://soaplite.com>.  I couldn't
>     agree more.  It's pretty awful code, and slogging through it to figure
>     out why it's doing something wrong is way too cumbersome.
> 
>     I just discovered an ugly little bug today with how WSDLs are converted
>     into code, and how parameter handling is (to be blunt) broken.  The fix
>     however, is even uglier.
> 
>     If work on a rewrite is underway, I'm interested in contributing.
> 
>     Rob
> 

Re: [Soaplite-devel] State of the SOAP

[Robert L. <rla...@ao...>]

Sure, that's a valid sentiment.  And I was tempted to do just that.  But 
that's also how SOAP::Lite became the mess that it is, and I didn't want 
to make another mess.  :(

Rob

Leo Lapworth wrote:
> 
> 
>     <snip>
> 
>     only then would development commence on the module itself.
> 
> 
>  
> Might I suggest (and this is not me offering) that someone just get on, 
> set up an SVN server, and start coding tests, then something might 
> actually happen :)
> 
> Leo
> 
> p.s. I'm happy to alter / have replaced anything in SOAP::XML::Client to 
> use what ever this new thing ends up being
> 
> p.p.s good luck!
> 

Re: [Soaplite-devel] State of the SOAP

[Robert L. <rla...@ao...>]

Mike South wrote:
> Right now there is a patch waiting which will let you generate stub
> code for a service that publishes a wsdl.  I think that the first
> order of business would be to apply (or reject with reasons) the
> outstanding patches.  

Maintenance should be separate from this process, at least initially. 
Combining the two into a single "project" will only create confusion for 
developers/maintainers.

> If the current maintainer doesn't have time to
> maintain it, he should be passing it off.

Agreed.  Has anyone stepped forward to take the torch?  From what I've 
read, SOAP::Lite is maintained only so that maintainer's current SOAP 
implementation isn't broken.  And that's the level of commitment most of 
us would be willing to provide too.  Finding someone willing to go the 
extra mile to make it right, to maintain it properly, is the challenge.

> Writing a new module is
> also a good idea, but imho we need to get maintenance of the current
> code running in parallel.  Right now that is stalled.
> 

Maintenance is a tricky thing.  Adding patches creates instability, 
which can lead to more maintenance.  I can understand why it's been slow 
in coming.

Rob

[Soaplite-devel] Fwd: Kicking off SOAP::Easy

[Charlie B. <cha...@gm...>]

I always forget the reply all for this list.  This message was sent to byrne
when it should have went to the entire list

---------- Forwarded message ----------
From: Charlie Bowman <cha...@gm...>
Date: Feb 21, 2007 9:35 AM
Subject: Re: Kicking off SOAP::Easy
To: Byrne Reese <by...@ma...>

I'll go first.

My number 1 pet peave with soap::lite is it's inability to handle complex
objects when using a wsdl.

On 2/20/07, Byrne Reese <by...@ma...> wrote:
>
> Very well. Let me play Product Manager then.
>
> The first steps in solving any problem is to clearly identify the
> problem. So let me begin by asking, and forgive the apparent obviousness
> of this first question, what do we not like about SOAP::Lite that we
> want to fix?
>
> And let's judge by the responses how many people are interested in
> helping?
>
> Byrne
>
> Charlie Bowman wrote:
> > I think a lot of people are wanting to help, I know I am.  What we
> > need is a little leadership to help get the ball rolling.
> >
> > On 2/16/07, *Robert Landrum* < rla...@ao...
> > <mailto: rla...@ao...>> wrote:
> >
> >     I just read the State of the SOAP post on soaplite.com
> >     <http://soaplite.com>.  I couldn't
> >     agree more.  It's pretty awful code, and slogging through it to
> figure
> >     out why it's doing something wrong is way too cumbersome.
> >
> >     I just discovered an ugly little bug today with how WSDLs are
> >     converted
> >     into code, and how parameter handling is (to be blunt)
> >     broken.  The fix
> >     however, is even uglier.
> >
> >     If work on a rewrite is underway, I'm interested in contributing.
> >
> >     Rob
> >
> >
> -------------------------------------------------------------------------
> >
> >     Take Surveys. Earn Cash. Influence the Future of IT
> >     Join SourceForge.net 's Techsay panel and you'll get the chance to
> >     share your
> >     opinions on IT & business topics through brief surveys-and earn cash
> >
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> >     <http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> >
> >     _______________________________________________
> >     Soaplite-devel mailing list
> >     Soa...@li...
> >     <mailto: Soa...@li...>
> >     https://lists.sourceforge.net/lists/listinfo/soaplite-devel
> >     <https://lists.sourceforge.net/lists/listinfo/soaplite-devel>
> >
> >
> > ------------------------------------------------------------------------
>
> >
> >
> -------------------------------------------------------------------------
> > Take Surveys. Earn Cash. Influence the Future of IT
> > Join SourceForge.net's Techsay panel and you'll get the chance to share
> your
> > opinions on IT & business topics through brief surveys-and earn cash
> > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > Soaplite-devel mailing list
> > Soa...@li...
> > https://lists.sourceforge.net/lists/listinfo/soaplite-devel
> >
>
>