Re: Taking your application out of CGI::Application (skinny run modes)

Yup, that's the approach I took in CGI::Prototype, many years ago. It has worked very well.

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.

Comment on Re: Taking your application out of CGI::Application (skinny run modes)

Replies are listed 'Best First'.
Re^2: Taking your application out of CGI::Application (skinny run modes) by ysth (Canon) on May 05, 2009 at 09:16 UTC
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119. But what does "are to be" mean? -- Online Fortune Cookie Search Office Space merchandise	[reply]
Re^3: Taking your application out of CGI::Application (skinny run modes) by merlyn (Sage) on May 08, 2009 at 20:27 UTC
But what does "are to be" mean? Oddly enough, RFC2119 doesn't explain further. {grin} -- Randal L. Schwartz, Perl hacker The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.	[reply]