SOAP::Lite for Perl

Moved to TypePad...

One of the advantages of being the Product Manager of TypePad is the fact that I get a free account to host my pet projects. Although I didn't move SOAP::Lite over to TypePad just for fun. One of the biggest advantages of this move is the excellent comment spam filtering that TypePad offers. Because TypePad is a hosted weblogging service, it can detect, block and delete comment spam globally for all weblogs on the service. Furthermore, because I am in TypePad almost every day now, it may compel me to keep the community up to date more.

And hey, before I forget: be sure to check out the latest HOWTOs about SOAP::Lite 0.65! I am starting a new series which I hope will start to educate the developer community a bit on some of the cool new features.

stubmaker.pl gets some updates

I just finished checking in some enhancements to stubmaker.pl. Nothing fancy, just improving the help documentation and added some command line switches so that you can control what directory generated files get outputed to. The new version of stubmaker will be released with the next beta of SOAP::Lite.

An improved HTTP Daemon?

I spent some time this weekend going through SOAP::Lite bugs, and I am so impressed with the S::L developer community! Almost all of the bugs contain patches of some kind. I can't tell you how wonderful it is (as the developer on a project like this) to have your users essentially doing your job for you! So thank you.

But that is not the point of this post. In one of the bugs a user, Michael Douglass to be exact, submitted what appears to be an improved implementation of SOAP::Transport::HTTP::Daemon. I am not ready to include the code in 0.65, but thought I would share it with the community and see if I can't get it to endorse it somehow so that I might include it in a later release.

I will test it eventually, but I am focusing on 0.65_3 right now and don't have the bandwidth for new features like this. Furthermore, I tend to avoid writing an HTTP daemon in Perl when I can use Apache for free. I would be curious to know why so many SOAP::Lite developers like using their own home grown HTTP daemon when there are so many good free ones available. Anyone care to shed some light on this?

Unlocking 0.65: Direct access to the HTTP::Request and HTTP::Response objects

I had no idea what I was getting myself into when I said I would take the reigns of the SOAP::Lite project. SOAP::Lite is an extensive module that feels like it grew quite organically. It is infused with some of the most creative Perl I have ever seen, and it took me two years of sporadic and at times intense development to even begin to unravel and make sense of the code. As a result, most SOAP::Lite releases have focused on areas of code which I was already intimately familiar, i.e. the MIME section, or with relatively minor bug fixes. But with 0.65 I pledged to tackle some of the issues that have long frustrated me. Over the next couple of weeks I will introduce a series of articles that explores some of the enhancements I have made to SOAP::Lite 0.65.