specifically chosen by you, to the end of an email or newsgroup posting,
or to the clipboard for pasting into a Web-based email or message board.
What is a tagline?
A tagline is a one-line joke, witticism, factoid, what have you. It can
be about any subject (although it's good to ensure it's appropriate to
the forum in question). The random quotes that can be found at the end
of web pages like Slashdot or the MozDev home page could be considered
taglines.
WWW: http://tagzilla.mozdev.org/
PR: ports/151360
Submitted by: Lapo Luchini <lapo at lapo.it>
client side scripting language can be used to create application level
logic and services for cross platform application development.
By creating libraries of common useful routines, application developers can
focus on creating original functionality for their own applications instead
of dealing w/ complex xpconnect wrapper objects and worrying about which
IDL methods do what and which are implemented on what platforms.
Goal: jslib has a simple goal, "Make life easier for Mozilla Application
Development by creating logical, easy to use API's for general purpose
routines that lend themselves to living in library code."
WWW: http://jslib.mozdev.org/
PR: ports/151359
Submitted by: Lapo Luchini <lapo at lapo.it>
into an easy to consume and extend role. It is based on previous POEx
work such as POEx::Role::TCPServer which provides basic TCP socket
multiplexing via POE::Wheel::SocketFactory and POE::Wheel::ReadWrite,
and POEx::Role::SessionInstantiation which transforms plain Moose
objects into POE sessions.
WWW: http://search.cpan.org/dist/POEx-Role-PSGIServer/
SocketFactory/ReadWrite combination of wheels into a simple
Moose::Role. It builds upon other POEx modules such as
POEx::Role::SessionInstantiation and POEx::Types.
The events for SocketFactory for and for each ReadWrite instantiated
are methods that can be advised in any way deemed fit. Advising these
methods is actually encouraged and can simplify code for the consumer.
The only method that must be provided by the consuming class is
handle_inbound_data.
WWW: http://search.cpan.org/dist/POEx-Role-TCPServer/
one filehandle to another. It accomplishes this by making good use of
sysread and POE::Wheel::ReadWrite. This Role errs on the side of
doing as many blocking reads of the "input_handle" as possible up
front (until the high water mark is hit on the Wheel). If this
default isn't suitable for the consumer, simply override
"get_data_from_input_handle". After Streamer has exhausted the
source, and flushed the last of the output, it will clean up after
itself by closing the wheel, the handles, and sending all of them out
of scope. If an exception happens, it will clean up after itself, and
let the DIE signal propagate.
WWW: http://search.cpan.org/dist/POEx-Role-Streaming/
