comment on

Having multiple developers work on a single file is only a problem if you have no version control, or are making massive changes.
A well-written CGI::Application module would not have much in the main class. It would be calling other classes to do most of the work. The main class just translates web requests into method calls on other classes.
Any project large enough to have a team working on it will have multiple CGI::Application modules. I like to split things up into logical "applications" so that if Jane is working on the address book app and Jim is working on the calendar, those will be separate modules.
In practice, I've never had a problem with teams using any kind of MVC approach like CGI::Application.

In reply to Re: CGI::Application in a team development environment by perrin
in thread CGI::Application in a team development environment by jeyroz

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		`&`
	<		`<`
	>		`>`
	[		`[`
	]		`]`

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.