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

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.
  • I have used an inhouse (and now buried in a dead company graveyard) CRUD system that autogenerated the right widgets and UI to match any java applet for interactivity.

    You could quite trivially build a full crud UI using DHTML and javascript rpc/rest calls to the server, storing some state information in javascript and calling the server only for object persistence and retrieval.

    I've seen it done over 18 months ago and we rebuilt it again from scratch. I think it would be as quick and easy as doing it in java.

    --

    @JAPH = qw(Hacker Perl Another Just);
    print reverse @JAPH;
    • I totally agree that java would be a massive overkill for a simple crud only UI, however the design requirements, and the scale of the objects involved mean that an autogenerated UI isn't practical in this instance.

      Perhaps starting again, taking onboard lessons learnt, but still using DHTML and javascript would offer some improvements, but I can also see some strengths ( if starting again ) in moving to a soap/java application to provide the UI ( rather than an applet ), and being naturally curious I'm ke
      • It was an inhouse development version, but the full application we built and my friends have built again (over a weekend) were for very large scale systems.

        There is very little you can do in a Java client you couldn't acheive with a DHTML application.

        Using a full webservice with a proper webservice client in the java client would be massive overkill - admittedly it would be less cumbersome and bloated than using CORBA but would be much heavier on the client than DHTML and XML/RPC.

        --

        @JAPH = qw(Hacker Perl Another Just);
        print reverse @JAPH;
        • I was wondering if you had experiences of developing ( or attempting to develop ) java soap clients for use with perl web services - its not an area where I can find a great deal of material, and there seem to be a number of different approaches that one can take, so even a few words of experience would help out greatly ( Is there a particular set of libraries you found cumbersome, for example )?