view release on metacpan or  search on metacpan

Copying  view on Meta::CPAN

		     END OF TERMS AND CONDITIONS

	Appendix: How to Apply These Terms to Your New Programs

  If you develop a new program, and you want it to be of the greatest
possible use to humanity, the best way to achieve this is to make it
free software which everyone can redistribute and change under these
terms.

  To do so, attach the following notices to the program.  It is safest to
attach them to the start of each source file to most effectively convey

 view release on metacpan or  search on metacpan

LICENSE  view on Meta::CPAN

		     END OF TERMS AND CONDITIONS

	Appendix: How to Apply These Terms to Your New Programs

  If you develop a new program, and you want it to be of the greatest
possible use to humanity, the best way to achieve this is to make it
free software which everyone can redistribute and change under these
terms.

  To do so, attach the following notices to the program.  It is safest to
attach them to the start of each source file to most effectively convey

 view release on metacpan or  search on metacpan

Makefile.old  view on Meta::CPAN

DISTVNAME = $(DISTNAME)-$(VERSION)
TAR  = tar
TARFLAGS = cvf
ZIP  = zip
ZIPFLAGS = -r
COMPRESS = gzip --best
SUFFIX = .gz
SHAR = shar
PREOP = @$(NOOP)
POSTOP = @$(NOOP)
TO_UNIX = @$(NOOP)
CI = ci -u
RCS_LABEL = rcs -Nv$(VERSION_SYM): -q
DIST_CP = best
DIST_DEFAULT = tardist


# --- MakeMaker macro section:

 view release on metacpan or  search on metacpan

LICENSE  view on Meta::CPAN

                     END OF TERMS AND CONDITIONS

        Appendix: How to Apply These Terms to Your New Programs

  If you develop a new program, and you want it to be of the greatest
possible use to humanity, the best way to achieve this is to make it
free software which everyone can redistribute and change under these
terms.

  To do so, attach the following notices to the program.  It is safest to
attach them to the start of each source file to most effectively convey

 view release on metacpan or  search on metacpan

PAR/Static.pm  view on Meta::CPAN

=item * Content served via Apache::PAR::Static with memory caching: 111 req/sec.

=back

You may want to play around with the various caching schemes to determing which one is best for your situation.  A quick comparison chart is below of the various caching schemes:

=over 4

=item * memory: Fastest access, most memory consumed

 view release on metacpan or  search on metacpan

LICENSE  view on Meta::CPAN

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. 

 

 view release on metacpan or  search on metacpan

ProxyRewrite.pm  view on Meta::CPAN

=over 4

=item B<Embedded Languages>

Embedded languages such as Javascript are not parsed for embedded
URLs. The problem is NP-Complete. The best choice is to surround
all embedded languages in HTML comments to avoid possible parsing
problems.

=back

 view release on metacpan or  search on metacpan

lib/Apache/SSI.pm  view on Meta::CPAN

"::" (this forces the function to be in the main package, or a package
you specify).  Note that it's a pretty bad idea to put your code in
the main package, so I only halfheartedly endorse this feature.

In general, it will be slower to use anonymous subroutines, because
each one has to be eval()'ed and there is no caching.  For best
results, pre-load any code you need in the parent process, then call
it by name.

If you're calling a subroutine like "&Package::SubPack::handler", you
can omit the "handler" portion, making your directive like this:

 view release on metacpan or  search on metacpan

lib/Apache/SdnFw/js/tinymce/changelog.txt  view on Meta::CPAN

Version 3.2.2.2 (2009-03-25)
	Fixed so the DOMUtils getPos method can be used cross documents if needed.
	Fixed bug where undo/redo wasn't working correctly in Gecko browsers.
Version 3.2.2.1 (2009-03-19)
	Added support for tel: URL prefixes. Even though this doesn't match any official RFC.
	Fixed so the select method of the Selection class selects the first best suitable contents.
	Fixed bug where the regexps for www. prefixes for link and advlink dialogs would match wwwX.
	Fixed bug where the preview dialog would fail to open if the content_css wasn't defined. Patch contributed by David Bildström (ChronoZ).
	Fixed bug where editors wasn't converted in application/xhtml+xml mode due to an issue with Sizzle.
	Fixed bug where alignment would fail if multiple lines where selected.
	Updated Sizzle engine to the latest version, this version fixes a few bugs that was reported.

 view release on metacpan or  search on metacpan

COPYING  view on Meta::CPAN

		     END OF TERMS AND CONDITIONS

	    How to Apply These Terms to Your New Programs

  If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.

  To do so, attach the following notices to the program.  It is safest
to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least