Apache-PageKit
view release on metacpan or search on metacpan
3.4.1. Third Party Claims. If You have knowledge that a party claims an intellectual property right in particular
functionality or code (or its utilization under this License), you must include a text file with the source code
distribution titled "LEGAL" which describes the claim and the party making the claim in sufficient detail that a
recipient will know whom to contact. If you obtain such knowledge after You make Your Modification available as
described in Section 3.2, You shall promptly modify the LEGAL file in all copies You make available thereafter and
shall take other steps (such as notifying AnIdea and appropriate mailing lists or newsgroups) reasonably
calculated to inform those who received the Governed Code that new knowledge has been obtained. In the event that
You are a Contributor, You represent that, except as disclosed in the LEGAL file, your Modifications are your original
creations and, to the best of your knowledge, no third party has any claim (including but not limited to intellectual
property claims) relating to your Modifications. You represent that the LEGAL file includes complete details of any
license or other restriction associated with any part of your Modifications.
3.4.2. Contributor APIs. If Your Modification is an application programming interface and You own or control
patents which are reasonably necessary to implement that API, you must also include this information in the LEGAL
file.
- Easy Error Handling
- Online Editing Tools
- Page based sessions
- Localized error/messages
Requirements
------------
- perl 5.005 or greater
- mod_perl 1.24_01 (lastest version requir'd for make test only)
- Apache 1.3.x (at best compiled _without_ expat (1.3.21 or higher recommended))
- Apache::libapreq
- Apache::SessionX
- Compress::Zlib
- Data::FormValidator
- Digest::MD5
- HTML::FillInForm 0.12
- HTML::Template 2.2
- HTML::Template::XPath
- HTML::Clean
docsrc/features.xml view on Meta::CPAN
</para>
</listitem>
</itemizedlist>
<para>
This approach parallels the division of the job responsibilities of a large web development team.
The programmers can focus on the Model, the designers on the View, and the content
administrators on the (you guessed it!) Content. PageKit provides the Controller which glues
everything together.
</para>
<para>
This way everybody can focus on what they do best, whether it is programming, design, or
content. Since the interfaces are simple and well-defined they can easily work together without
interfering with each other.
</para>
<sect2>
<title>Model</title>
<para>
The Model is provided by Perl classes which implement the business logic that is custom to the
site. These class files should be located in the <filename>Model/</filename> directory. Each URL is translated into a class and method automatically.
</para>
<para>
docsrc/reference.xml view on Meta::CPAN
<para>
pkit_on_error main purpose is to catch errors for some reason. Maybe you can not
get a database connection or your page can not be delivered in a special
charset or anywhere inside your modelcode an uncatched die "for unknown
reason"; is executed.
</para>
<para>
If nowhere else in your code this error is handled, pkit_on_error is called
with the error message as second parameter and model as the first. This is
your chance to deliver a working page. At best with pkit_redirect or pkit_send.
</para>
<para>
If an error happened inside pkit_on_error it is passed thru Apache and you get the internal server
error as before. pkit_on_error returns the error_msg that is logged. So you
can change the messsage if you like. If the returned error_msg is '' or undef
nothing is logged and pkit assumes, that the error is repaired. If you like
to log anyway add a warn $error_msg"; inside your pkit_on_error routine.
</para>
<para>
Also pkit_on_error is no replacement for Apache::ErrorReport. pkit_on_error
eg/View/Default/license.tmpl view on Meta::CPAN
<B><P ALIGN="JUSTIFY">3. Distribution Obligations. </P>
</B><P ALIGN="JUSTIFY"> </P>
<B><P ALIGN="JUSTIFY"> 	3.1. 	Application of License. </B>The Modifications which You create or to which You contribute are governed by the terms of this License, including without limitation Section 2.2. The Source Code version of Govern...
<P ALIGN="JUSTIFY"> </P>
<B><P ALIGN="JUSTIFY"> 	3.2. 	Availability of Source Code. </B>Any Modification which You create or to which You contribute must be made available in Source Code form under the terms of this License either on the same media as an Executabl...
<P ALIGN="JUSTIFY"> </P>
<B><P ALIGN="JUSTIFY"> 	3.3. Description of Modifications. </B>You must cause all Governed Code to which you contribute to contain a file documenting the changes You made to create that Governed Code and the date of any change. You must incl...
<P ALIGN="JUSTIFY"> </P>
<B><P ALIGN="JUSTIFY"> 	3.4. Intellectual Property Matters. </P>
</B><P ALIGN="JUSTIFY"> </P>
<P ALIGN="JUSTIFY"> 		<B>3.4.1.	Third Party Claims.</B> If You have knowledge that a party claims an intellectual property right in particular functionality or code (or its utilization under this License), you must include a text f...
<P ALIGN="JUSTIFY"> </P>
<P ALIGN="JUSTIFY"> 		<B>3.4.2. 	Contributor APIs.</B> If Your Modification is an application programming interface and You own or control patents which are reasonably necessary to implement that API, you must also include this inf...
<P ALIGN="JUSTIFY"> </P>
<B><P ALIGN="JUSTIFY"> 	3.5. 	Required Notices. </B>You must duplicate the notice in Exhibit A in each file of the Source Code, and this License in any documentation for the Source Code, where You describe recipients' rights relating to Go...
<P ALIGN="JUSTIFY"> </P>
<B><P ALIGN="JUSTIFY"> 	3.6. 	Distribution of Executable Code Versions. </B>You may distribute Governed Code in Executable Code form only if the requirements of Section 3.1-3.5 have been met for that Governed Code, and if You include a pro...
<P ALIGN="JUSTIFY"> </P>
<B><P ALIGN="JUSTIFY"> 	3.7. 	Larger Works. </B>You may create a Larger Work by combining Governed Code with other code not governed by the terms of this License and distribute the Larger Work as a single product. In such a case, You must...
<P ALIGN="JUSTIFY">	</P>
<B><P ALIGN="JUSTIFY">4. 	Inability to Comply Due to Statute or Regulation. </P>
( run in 0.380 second using v1.01-cache-2.11-cpan-501359838a1 )