Result:
found more than 1264 distributions - search limited to the first 2001 files matching your query
( run in 1.206 )
AnyEvent-WebSocket-Client
view release on metacpan or search on metacpan
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
AnyEvent-XMPP-Ext-HTML
view release on metacpan or search on metacpan
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
AnyEvent-XMPP
view release on metacpan or search on metacpan
lib/AnyEvent/XMPP.pm view on Meta::CPAN
deprecated!
Rewrote the low-level socket stuff to use L<AnyEvent::Socket> and L<AnyEvent::Handle>.
Removed blocking write functionality, which can't be supported that
easily with L<AnyEvent::Handle> (however, if you want to wait until the send-buffer
is empty you best use the C<send_buffer_empty> event of L<AnyEvent::XMPP::Connection>).
For more details consult the Changes file of the AnyEvent::XMPP distribution.
=item * older
lib/AnyEvent/XMPP.pm view on Meta::CPAN
or feature requests. I won't forget the reports or requests if you can't or
didn't send patches, but I can't gurantee immediate response. But I will of
course try to fix/implement them as soon as possible!
Also try to be as precise as possible with bug reports, if you can't send a
patch, it would be best if you find out which code doesn't work and tell me
why.
Please report any bugs or feature requests to
C<bug-net-xmpp2 at rt.cpan.org>, or through the web interface at
L<http://rt.cpan.org/NoAuth/ReportBug.html?Queue=AnyEvent-XMPP>.
AnyEvent-XSPromises
view release on metacpan or search on metacpan
lib/AnyEvent/XSPromises.pm view on Meta::CPAN
=over
=item Promises
L<Promises> is a pure-Perl Promises implementation that allows selecting one of multiple event loop backends. However,
this backend is defined globally and the documentation suggests that it would be best if only the application developer
picks a backend. This means that libraries cannot know up front which event loop backend they have to use, and they need
to support all event loops or the library would break if a different event loop is chosen. This has lead library authors
to mandate that the selected backend is AnyEvent, defying the purpose of backend selection other than for usage in
scripts that do not need compatibility with other code such as libraries from CPAN.
AnyEvent-YACurl
view release on metacpan or search on metacpan
#ifndef IVSIZE
# ifdef LONGSIZE
# define IVSIZE LONGSIZE
# else
# define IVSIZE 4 /* A bold guess, but the best we can make. */
# endif
#endif
#ifndef UVTYPE
# define UVTYPE unsigned IVTYPE
#endif
#ifndef PERL_MAGIC_ext
# define PERL_MAGIC_ext '~'
#endif
/* That's the best we can do... */
#ifndef sv_catpvn_nomg
# define sv_catpvn_nomg sv_catpvn
#endif
#ifndef sv_catsv_nomg
AnyEvent-ZeroMQ
view release on metacpan or search on metacpan
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
AnyMerchant
view release on metacpan or search on metacpan
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
AnyMongo
view release on metacpan or search on metacpan
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
AnySan-Provider-Slack
view release on metacpan or search on metacpan
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
Aozora2Epub
view release on metacpan or search on metacpan
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
AozoraBunko-Checkerkun
view release on metacpan or search on metacpan
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
Apache-ASP
view release on metacpan or search on metacpan
default 0, if set and Time::HiRes is installed, will do
sub second timing of the time it takes Apache::ASP to process
a request. This will not include the time spent in the
session manager, nor modperl or Apache, and is only a
rough approximation at best.
If Debug is set also, you will get a comment in your
HTML output that indicates the time it took to process
that script.
# a simple value
$Response->{Cookies}{'Test Name'} = 'Test Value';
I prefer the hash notation for cookies, as this looks nice, and is
quite perlish. It is here to stay. The Cookie() routine is
very complex and does its best to allow access to the
underlying hash structure of the data. This is the best emulation
I could write trying to match the Collections functionality of
cookies in IIS ASP.
For more information on Cookies, please go to the source at
http://home.netscape.com/newsref/std/cookie_spec.html
Be careful not to expose full session ids over the net, as they
could be used by a hacker to impersonate another user. So when
creating a session manager, for example, you could create
some other id to reference the SessionID internally, which
would allow you to control the sessions. This kind of application
would best be served under a secure web server.
The ./site/eg/global_asa_demo.asp script makes use of this routine
to display all the data in current user sessions.
=item $Application->SessionCount()
=back
=head2 $Server Object
The server object is that object that handles everything the other
objects do not. The best part of the server object for Win32 users is
the CreateObject method which allows developers to create instances of
ActiveX components, like the ADO component.
=over
As of version 0.09, use of CGI.pm for both input and output is seamless
when working under Apache::ASP. Thus if you would like to port existing
cgi scripts over to Apache::ASP, all you need to do is wrap <% %> around
the script to get going. This functionality has been implemented so that
developers may have the best of both worlds when building their
web applications.
For more information about CGI.pm, please see the web site
http://search.cpan.org/dist/CGI/
> The ->{Item} property does not work, use the ->Item() method.
=head1 STYLE GUIDE
Here are some general style guidelines. Treat these as tips for
best practices on Apache::ASP development if you will.
=head2 UseStrict
One of perl's blessings is also its bane, variables do not need to be
declared, and are by default globally scoped. The problem with this in
like OpenLink Software (http://www.openlinksw.com/) provide the nuts and
bolts for ODBC.
Database connections can be cached per process with Apache::DBI.
=item What is the best way to debug an ASP application ?
There are lots of perl-ish tricks to make your life developing
and debugging an ASP application easier. For starters,
you will find some helpful hints by reading the
$Response->Debug() API extension, and the Debug
<a href=http://www.conceptonline.com><img src=concept_online.gif border=0></a>
=end html
I would like to say that your ASP module rocks :-) We have practically stopped developing in anything else about half a year ago, and are now using Apache::ASP extensively. I just love Perl, and whereever we are not "forced" to use JSP, we chose ASP....
-- Csongor Fagyal, Concept Online Ltd.
=item WebTime
Apache-Access-Headers
view release on metacpan or search on metacpan
This behavior is not yet configurable.
=head1 CONFIGURING APACHE
Module configuration is simple ( read: limited ). Currently, the module
only works with a single configuration file, and works best when configured
for a server's document root. See the LIMITATIONS section for an explanation
of the modules current short-comings.
Add the following line to httpd.conf outside all Directory,
Location and VirtualHost blocks:
Apache-App-Mercury
view release on metacpan or search on metacpan
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
Apache-AuthCAS
view release on metacpan or search on metacpan
Makefile.PL view on Meta::CPAN
'VERSION' => '0.5',
'PREREQ_PM' => { "Net::SSLeay" => 1,
"MIME::Base64" => 0,
"DBI" => 1
},
'dist' => { COMPRESS => 'gzip --best', SUFFIX => 'gz' },
'ABSTRACT_FROM' => 'lib/Apache/AuthCAS.pm',
'AUTHOR' => 'David Castro <dcastro@apu.edu>',
);
Apache-AuthChecker
view release on metacpan or search on metacpan
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 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
Apache-AuthCookie
view release on metacpan or search on metacpan
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
Apache-AuthTicket
view release on metacpan or search on metacpan
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
Apache-AuthenSecurID
view release on metacpan or search on metacpan
RCS/Makefile.old,v view on Meta::CPAN
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:
Apache-AxKit-Language-LibXSLTEnhanced
view release on metacpan or search on metacpan
lib/Apache/AxKit/Language/LibXSLTEnhanced.pm view on Meta::CPAN
L<Apache::AxKit::Language::LibXSLT>, L<AxKit>, L<Apache::AxKit::Util::LibXSLTAddonFunction>
=head1 AUTHOR
Tom Schindl, E<lt>tom.schindl@bestsolution.atE<gt>
=head1 COPYRIGHT AND LICENSE
Copyright (C) 2004 by Tom Schindl
Apache-AxKit-Language-Svg2AnyFormat
view release on metacpan or search on metacpan
lib/Apache/AxKit/Language/Svg2AnyFormat.pm view on Meta::CPAN
L<Apache::AxKit::Plugin::SvgCgiSerialize>
=head1 AUTHOR
Tom Schindl <tom.schindl@bestsolution.at>
=cut
Apache-AxKit-Plugin-Session
view release on metacpan or search on metacpan
lib/Apache/AxKit/Plugin/Session.pm view on Meta::CPAN
PerlSetVar AxKitSessionExpires +1d
PerlSetVar AxKitSessionDomain some.domain
PerlSetVar AxKitSessionSecure 1
Path can only be set to "/" if using URL sessions. Do not set "AxKitSessionExpires",
since the default value is best: it keeps the cookies until the user closes his
browser.
Disable cookies: (force URL-encoded sessions)
PerlSetVar AxKitSessionNoCookie 1
Apache-AxKit-Provider-RDBMS
view release on metacpan or search on metacpan
lib/Apache/AxKit/Provider/RDBMS.pm view on Meta::CPAN
=back
=head1 AUTHOR
Tom Schindl, <lt>tom.schindl@bestsolution.at<gt>
=head1 COPYRIGHT AND LICENSE
Copyright (C) 2005 by Tom Schindl
Apache-BabyConnect
view release on metacpan or search on metacpan
lib/Apache/BabyConnect.pm view on Meta::CPAN
=head1 DESCRIPTION
This module initiates persistent database connections using DBI::BabyConnect.
This module is best understood by going through the roadmap file and the
sample programs provided with this distribution. The roadmap file is
eg/README, and the sample programs are in eg/perl.
When loading the Apache::BabyConnect module, the
module looks if the environment variable BABYCONNECT has been set to the
Apache-Backhand
view release on metacpan or search on metacpan
Backhand.pm view on Meta::CPAN
As explained above, you cannot PerlModule or use() or require()
Apache::Backhand until *after* mod_backhand (and mod_perl, of course) are
linked into the server.
As explained above, you cannot call load_serverstats() until *after* the
shared memory segment has been created and attached. The best place to do
this is the child init phase.
It's easy to make mod_backhand coredump by doing Bad Things to serverstats
(e.g. 'foreach (@{$serverstats}) { $_->{'mtime'} = time() }'...)
Even though I've provided the magic to make serverstats writeable, this should
Apache-BalancerManager
view release on metacpan or search on metacpan
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
Apache-CodeRed
view release on metacpan or search on metacpan
* Makefile.PL: Added prerequisites, so that CPAN.pm and other
installation tools will let you know if you need the latest
versions of various modules. Truth be told, I'm not sure what the
minimum versions are for the required modules, so I just set them
to the current values and will hope for the best.
* CodeRed.pm: What didn't I do? I wrote some POD, gave the module
a new name (Apache::CodeRed, rather than plain ol' CodeRed),
retooled a few basic things, removed some bugs.
Apache-CryptHash
view release on metacpan or search on metacpan
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
Apache-DBI-Cache
view release on metacpan or search on metacpan
USAGE
Different to Apache::DBI Apache::DBI::Cache must be "use"ed not
"require"ed. That means it's "import" function must be called.
When used with mod_perl (versions 1.x or 2.x) this is best done in a
"startup.pl" or in a "<Perl>" section in the "httpd.conf". See mod_perl
documentation for more information.
Thereafter, "DBI->connect" is called as usual. No special treatment is
needed.
Apache-DBILogin
view release on metacpan or search on metacpan
DBILogin.pm view on Meta::CPAN
The database user's clear text passwd is made available in the
server's environment. Do you trust your developers?
=head1 BUGS
Probably lots, I'm not the best programmer in the world.
=head1 NOTES
Feel free to email me with comments, suggestions, flames. Its the
only way I'll become a better programmer.
( run in 1.206 second using v1.01-cache-2.11-cpan-39bf76dae61 )