in reply to Encapsulating web client side code in Perl modules?

In Kayuda, we found it helpful to look at this problem slightly differently. You have the server and it exposes a rather generic API. You then have clients that consume that API. Now, you might only write one of these clients (your web client), but by making that separation, life was a lot easier.

And, Javascript isn't bad, particularly if you are using the Dojo toolkit.

My criteria for good software:
  1. Does it work?
  2. Can someone else come in, make a change, and be reasonably certain no bugs were introduced?
  • Comment on Re: Encapsulating web client side code in Perl modules?

Replies are listed 'Best First'.
Re^2: Encapsulating web client side code in Perl modules?
by mpeters (Chaplain) on May 08, 2007 at 21:33 UTC
    And, Javascript isn't bad, particularly if you are using the Dojo toolkit.
    Really any good (Prototype, MooTools, JQuery, etc) JS toolkit will make it pretty easy to work with.

    -- More people are killed every year by pigs than by sharks, which shows you how good we are at evaluating risk. -- Bruce Schneier
[reply]

In Section Meditations