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've been finding I have something of this problem with ORLite, which is intended to give you a reasonable full ORM in one line of code.

    The problem is that it isn't documented like regular code is documented. It just lets you call stuff based on the database structure, and I'm finding that very very annoying.

    Apart from automatically generating POD for the documentation, I'm stuck at this point.

    • Alzabo did something similar, and I did write a complete POD generator.

      However, it's a little different in this case, because it's generating an API based on a database you know about, so if the rules for API generation are predictable, knowing what the API will be is simple.

      If you're writing a client for a REST service, you only know what the providers of the service tell you.

  • Just take the ideas you like about REST, build your API as you see fit and call it something else. POX/HTTP, or whatever.