Postmaster Meets XML-RPC
Skip this if you care nothing for technology-speak. There’s nothing in this post that you will find of the slightest interest.
Now that we’re rid of the riff-raff: Postmaster has seen several interesting changes recently, a shift in methodology, actually, worthy of mention here.
The Initial Problem:
Many existing weblog systems lack the ease-of-use editing features found in most word processors. Think buttons to make text bold or italics (and matching shortcut control keys). Buttons to insert links, images. Simple things you take for granted elsewhere, but are found lacking in traditional web interfaces.
Solution #1’s Downfall
The solution needed for Postmaster needs to be cross-platform. Compliant. Standards based. An asterisk indicating incompatabilities won’t do.
Create a Java applet. You’ll have absolute control over the look and feel, the responsiveness, the featureset. It’ll be much harder to develop, but now Postmaster will run anywhere Java will (and that’s just about everywhere). Plus, you’ll be able to reuse your new components when you roll-out the actual Postmaster desktop app.
Solution #2’s Downfall
Use XML-RPC. Make the applet speak to the servlet directly. Cut out the middle-man. The server receives the XML-RPC data, responds to it, and returns a response. The Applet responds by redirecting the browser to a dynamic response page.
Those of you nodding your head knowingly, go pat yourself on the back, rearrange your pocket protectors, set your protractors, and treat yourself to another Pop-Tart. The rest of you, rejoice in the improvement of an application you will soon enjoy.