comment on

++ for the thought and effort, this is an admirable decomposition of web development.

If only it was attainable. The manager, designer, or both are going to demand something that is utterly irresponsible to give them. It may be an open mail relay ("I can get that from Matt's Script Archive, why can't you do it? What do I need you for!"), a free shell account dispenser, or a convenient ftp upload site with public access. They have the power of the purse, so your warnings indicate the kind of commercial cowardace that consigned you to peonage in the first place.

Try to obtain contracts where the managers go lightly and the designers can remember ASC mode of ftp. Make sure the managers wishes are approved by, and can be vetoed by, competent sysadmins on their host.

After Compline,
Zaxo

In reply to Re: XSL/XML/Perl as a development process by Zaxo
in thread <strike>XSL/XML/Perl as a development process</strike> by chunlou

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Just another Perl shrine
	PerlMonks