Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

darobin (1316)

darobin
  (email not shown publicly)
http://berjon.com/

Journal of darobin (1316)

Sunday February 17, 2002
03:10 PM

Small SOAP wrapper to use Perl

[ #2927 ]

Making use of use Perl's new cool SOAP features, I've created a small, simple, and thin wrapper around them, if only to remember the interface. It has its quirks and limitations, but it works.

This is the first step in an attempt to create a WxPerl journal editor, when/if I get the time. You can grab it from http://berjon.com/src/SOAP.pm.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • This will be broken sometime in the near future. The interface is not set, which is why I haven't announced it.
    • I thought as much, but as far as I'm concerned I don't mind much. Developping the UI will take time, something which I don't have plenty of these days. And the wrapper is simple enough that it can probably be rewritten in a few minutes now and then :)

      One thing that I found missing in the interface is nick2uid mapping and/or the ability to use a nick instead of a uid when fetching entries. Apart from that, it's really cool.

      --

      -- Robin Berjon [berjon.com]

      • Re:Broken (Score:3, Interesting)

        The good thing about SOAP is that you point at a dummy proxy/endpoint while testing. And it's easy to do. So that should let you debug the wxPerly bits with the current interface in a stable state, and then debug the new interface when Pudge makes it public.

        Just $0.02. :-)

      • Re:Broken (Score:3, Informative)

        I don't know if I'll support that or not. Probably not now, just because it might part of a larger SOAP interface for Slash, and I don't want to add it only to remove it later. It would belong in some Users package, not in Journal. And it's easy to look up user IDs manually. ;-)

        Another thing might be an eventual Zoo interface (that which supplies the friends/foes stuff), to let you see who your friends/foes/etc. are, and maybe add and remove friends/foes. And this is why I don't want to move ahead too