Beefy Boxes and Bandwidth Generously Provided by pair Networks
The stupid question is the question not asked
 
PerlMonks  

RE: Design vs. Code vs. Maintenance

by lhoward (Vicar)
on May 17, 2000 at 18:42 UTC ( [id://12096]=note: print w/replies, xml ) Need Help??


in reply to Design vs. Code vs. Maintenance

If you can get HTML::Template on your server it supports almost exactly the "parse template/fill in content" methodology that you've just described (only the tag format is slightly different):
<TMPL_VAR NAME=PATH>
In response to your original question :
Considering that most webhosting companies do not offer solutions such as embperl, Mason, Apache::ASP or others of the sort, what is the most efficient way to work with, build and maintain these websites?
I would not let "webhosting feature availability" influence my decisions in any major way when it came to features that would severly affect the design, development, maintenance, architecture, scalability, and performance of a site. I first decide what are the right tools to use to make the site then ask who can provide me with these tools. If a company can afford a 7 person team to develop a website then they can surely afford to get server(s) configured they way they require to run the site. You are already placing requirements on the server by making the choices of perl, DBI, and a database (w/ apropriate DBD module). Requiring a few additional perl or apache modules is not asking too much. Making an architectural decision of such importance based on provider availability could lead to a support/maintenance nightmare later on. It is well worth it to do things properly up-front to save yourself pain later on. Choosing an inferior tool just because its convenient is not the right answer : I don't see any saws near-by, but I do have a bunch of hammers, so why don't I use one of them to cut this 2x4.

Webhosting is a competitive market and it sounds like you are developing a non-trivial site. Hosting your site could mean a lot of income to whichever web-hosting provider you use. They should be willing to provide you with the tools that you require in order to get your business. If "most webhosting companies do not offer" what you need seek out the ones that do and give them your business. Other developers will make the same choices as you and the providers that offer better services/features to the site development/maintenance team will flourish.

Replies are listed 'Best First'.
RE: RE: Design vs. Code vs. Maintenance
by BBQ (Curate) on May 17, 2000 at 20:29 UTC
    Yeah, I think I should have specified why my worry about webhosting providers. You see, many of our customers already come to us with a webhost that they have used in the past and are happy with. Its my company's policy not to vouch for other company's services, so we tend not to try and push them away from a service that they are already happy with.

    In some cases (our larger, corporate) clients own their own servers, but then its likely that I'll have to get it through to the thick-skulled-dinosaur-it-manager that compiling DBD::Oracle requires that you have at least Oracle client installed on his HP-UX (get the drift?).

    Bottom line is that unfortunately I am not always able to choose out of a vast quantity of hosting options, and that's why I got stuck with my MakeHTML($template,%HASH) solution. :o/

    Thank you for the great advice on HTML::Template, I've skimmed through and seems to be exactly what I was in need for! (and my most common webhost, HWay, has it in their module list)
      I understand getting stuck with a less-optimal solution because of choices made elsewhere. About all you can do it inform the client of the ramifications of their decision and prepare.

      In the first case I would handle it like this. Tell the client company:

      Since your current webhost doesn't support A, B, or C we can develop your project in X weeks and it will take about Y effort to support in the future. It will scale like Z. If you find a webhost that supports A, B, and C then we can implement it in T weeks and it will take about U effort to support in the future and it will scale like V.
      Break it down in such a way that both their operations staff and accounting departments can both understand the ramifications of the choice they've made. If they choose to stay, at least they know what tradeoff they made (and hopefully they'll come back to you when they realize the error of their ways). Also, if you can get your company to change policies and start recomending a (or some) particular webhost(s), you may be able to cut a deal w/ the webhost that would let the clients get a lower rate (since you'd be bringing them in in bulk).

      In the second case (and I've been in that EXACT same spot before w/ HP-UX and Oracle even). be sure you include in your specifications details requirements of what they must have installed (preferably in an early spec that upper-managemet signed-off on). Make sure this is widely distributed to all parties related to your project in the client company. Make sure you are ready so if it comes down to the dinosaur manager problem you can place blame squarely on his/her shoulders and show him/her that upper management has already signed-off on it. It still isn't a fun fight to have, but being prepared can make it an easier win.

        Hehe, I failed to mention that the 2nd case was while I was doing work for Oracle Brazil... :o) We are currently maintaining their site.

        On the 1st case though, that sounds like perfectly sound advise, and we've tried doing it the past. As I said, its much more of a company policy problem when their host goes down, or emails cease to work, or something else totally none web related and they come back at you for support since "it was your recomendation".

        As they say, "Now that's whay I call a sticky situation!"
RE: RE: Design vs. Code vs. Maintenance
by doran (Deacon) on May 17, 2000 at 19:44 UTC
    I too agree with lhoward about both HTML::Template and his views on choosing webhosts. I had been using custom "special" tags and then parsing this template. I've now begun using HTML::Template and am quite happy that I am. In addition to generally making HTML editing MUCH easier, it also allows for loops and some other nifty controls. Good luck, Doran

Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://12096]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others meditating upon the Monastery: (4)
As of 2024-03-29 10:10 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found