All the Perl that's Practical to Extract and Report

Navigation

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Without JavaScript enabled, you might want to
use the classic discussion system instead. If you login, you can remember this preference.

I believe so, and from what I hear it seems like an excellent piece of kit - however I feel that html, although a good medium, does not address the needs of the application(s) that I am looking to develop, hence the desire to look elsewhere.

Ahh! Yes, HTML/HTTP as the universal protocol leaves quite a bit to be desired (aside from Firewall pentetrability).

If you come up with something as elegant as Maypole but based around WSDL [developer.com] and the other WS* standards, that would be way cool. (Not that the standard SOAP over HTTP is much of an improvement protocol-wise, but it decouples at least.)

Would a hypothetical Maypole::SoapLite extension, probably using WSDL::Generator [cpan.org] and/or SOAP::WSDL [cpan.org] do anything for you?

FYI, although I haven't used it myself, in the Java universe, the hot light-weight client-side toolkit is now XUL [mozilla.org] using Moxilla/FireFox browser. (tutorial [xulplanet.com]). Think XML-based specification of TCL-like rich-but-thin GUIs that run in browsers? There's already a XUL::Node [cpan.org] class on CPAN for server-side XUL in Perl. Other Perl-Xul connections are in progress, PerlXUL [sourceforge.net] (advanced planning stage but dormant? [yahoo.com])and Perl-Xul (list) [yahoo.com].

Your original posting [perl.org]'s referenced articles' discussion of extensional CRUD versus intentional transactions is interesting. I need to think about this for a little web-app I'm planning to build to share updating the DB behind a query-only website. For that app, I probably have naturally optimistic concurrency -- no two people should want to update the same item at once -- so CRUD may be ok. Both CRUD and Transactional GUI+Engine stink if you have to stick-build every last screen or transaction; I'm looking for good easy tools. Maypole2 was the best I'd seen, but I need to re-think this, and quickly.

A "Maypole::SoapLite" module would be most usefull ( although I imagine the dependencies would cover a large part of CPAN ) - Almost a Holy Grail as far as this project is concerned. In terms of my own development, I haven't yet decided whether its best to base this on Maypole, or base it on the theories that Maypole is based upon, I think a fair bit of R&D will be required - especially in WSDL and XML schema.

Your comment about the decoupling effect provided by SOAP is one of the reasons I am consideri

Disclaimer: I work at the reg*.{[hc],sym} like a novice alchemist:
I pour the blue liquid on the red liquid. If it doesn't blow up on my
face, I proceed to turn up the flame under the blue liquid, and so on.
I have very little idea of what I am really doing, I just like the
pretty colors :-)
-- Jarkko Hietaniemi

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.