casino island blackjackcasino games prowww jeu de casinoforum jeux casino,jeux casino machines a sous,jeux casinocasino games pro 2007edfajeux baccarat gratuitesrent a car bulgariacasino en ligne comjeux virtuels casinocasino games becomment jouer au casinojeu video poker gratuitescasino machine a sous gratuitescasino blackjackmeilleurs casinos en ligneflash games casinocasino en lignesgagner casino en lignecasino gratuites gagnercasino partoucheкомпютри втора употребаdés crapscasino bonus de bienvenuejeux casino francaiscasinos onlinecasino en ligne bonusvideo slot machinecasino gratuites internet,droit de jouer au casino sur internet,casino internetrussian roulettejeu de casino machinecasino poker en lignecasino games 2007jeux roulette russeroulette en ligne gratuitesjeux gratuites casino machineдиваниtelecharger video poker gratuitesjeux casino 770casino netsalles virtuelles de jeux gratuitsjeux a roulettejeux flash casinowww supermarché casinoswww traiteur casino comcasino on net comjeu poker freewareles regles poker ferméjeu 7 card studjeux de poker virtueljeu flash gratuitesachat jeu de pokeronline casinojeux flashcomment apprendre ŕ jouer au poker

“…and saved my company tens-of-thousands of dollars in licensing and (worthless) support costs.”

Oh the lure of big name, high-dollar Java application servers. They have a long list of features and are backed by big companies with promise of big support. Unfortunately many of the features don’t work as advertised, the support is difficult to access or non-existant, and in the long run the things turn into holes in your server you throw money in. I’ve had the same experience as Ralph, taking a Websphere installation (that I recommended and spearheaded) over to Resin (which I also recommended, after a couple years of Websphere pain and suffering). The difference was night and day, reliability shot up immediately and deployments went from all day affairs (maybe it will start this time) to 15 minute finger-snaps (done). Can’t recommend Resin highly enough, imho.

Anyway, what went wrong with the large Java app server players? Why can’t they deliver reliable software, actual support, all within reasonable dollar ranges (were normally talking order-of-magnitude dollar differences, and some are processor number based)? Small companies and open-source seem able to do this quite readily.

The Meaning of Semantics

Great article from D. Keith Robinson (Asterisk) about the importance of content to a web project. Your web site can be considered a “content vehicle” (think brochure, billboard, article, etc.) with unique capabilities (incredibly timely, easily updated, free distribution, etc.). What good is a billboard without a message?

A Rant (Mostly) About Web Content

Eris | Standards in Design. Standards in Life

If you have a complex set of scripts/classes/etc. here are the things I would want to help my ‘real world ramp-up time’ with your code:

• A High-Level Diagram: nothing elaborate, but I want to see from a higher level how your code fits in with its surroundings (PHP, databases, directories, servers, etc.). If your documents dump me right in at the branches-on-trees levels it will take me days of dinking with it to see the actual forest, days I spend in frustration (why the heck is this needed here?…, etc.), or not (often the case).
• At least one real world, detailed example: So many scripts/classes/etc. come with the most God awful, trivial, only-uses-one-aspect-of-the-code examples. These are just worthless. Period. Even when they are correct (which very often they aren’t because the code base changes at a 2.5x rate compared to documentation). Just one real example can negate reams of missing documentation, really.
• If the script/class is of a framework-ish or application structure-ish type I would like to have a small (empty) reference implementation to start with. This should be structured using the ‘best practices’ for your code. This will give me something to hang test code on and will get me up to speed in very short order (even if I don’t understand what I’m doing yet). Be sure to take into account other ‘best practices’ when you set this up (normal web server layouts, code references, etc.), and document those that you don’t adhere to.
• And in my dream world, I would like to see actual documentation. That is documentation that has actual text (not just the method/function definitions and their undocumented parameters) describing the inner-workings of your exquisite, hand-crafted code base. Even sprinkle on some working example code snippets.

In his Hive announcement Paul stresses comprehensibility, which is definitely a positive trait in his other PHP efforts, and a very worthwhile goal that much of the PHP ’script’ world should aspire to. I’m glad he brings up this point in reference to Pear, as that is mostly what kept me from using Pear code for quite some time. Until you get over the Pear hump, Pear code is difficult to visualize. That is it isn’t apparent what Pear can offer you (or even what actually comprises Pear), what pieces/files you actually need if you think an element you’ve seen might be useful, or how to actually get the elements. Much of this could be remedied (disregarding actual package code complexity) at the Pear web site level, which suffers from a lack of higher-level information or documentation.

• Nathan Gunn
• UI CRME (Council for Research in Music Education)

All three of these great tools come from Paul Jones, who from the looks of his other projects is quite a busy developer.

Yawp: It’s not a framework but a well thought out class that helps pull together common PHP web development pieces. It is centered around a file-based configuration file which fronts useful tools from Pear and elsewhere. From that configuration file it is easy to setup Error handling, Database Abstraction, Templating systems, Debugging tools, etc.

DB Table: A small footprint Database Abstraction layer which is a Pear project. DB Table encapsulates the table/field definitions and table specific SQL code. It in turn uses the Yawp configured DB (Pear) database connection classes to interface with the database. It can also generate a Pear HTML QuickForms form from the same field definitions, making basic form processing very quick to develop.

Savant2: This is the first of Paul’s projects that I started using. It was an offshoot of some templating code that Brian Lozier had published a couple of years ago, following an article by Harry Fuecks (whew). Before Savant I had cleaned up Brian’s original code and used it in a few projects with great success. Savant takes PHP as Templating language idea quite a bit farther, rolling it into an Object Oriented structure and adding plugins and filters. It makes templating a site and incorporating dynamic site features a very straightforward operation and I have used it on all my recent projects.