Ports Search

How does Pod::WSDL work? If you instantiate a Pod::WSDL object with the name of the module (or the path of the file, or an open filehandle) providing the web service like this my $pwsdl = new Pod::WSDL(source => 'My::Module', location => 'http://my.services.location/on/the/web'); Pod::WSDL will try to find "My::Module" in @INC, open the file, parse it for WSDL directives and prepare the information for WSDL output. By calling $pwsdl->WSDL; Pod::WSDL will output the WSDL document. That's it.

This module implements an XML diff producing XML output. Both input and output are DOM documents, as implemented by XML::LibXML. The diff format used by XML::DifferenceMarkup is meant to be human-readable (i.e. simple, as opposed to short) - basically the diff is a subset of the input trees, annotated with instruction element nodes specifying how to convert the source tree to the target by inserting and deleting nodes. To prevent name colisions with input trees, all added elements are in a namespace http://www.locus.cz/XML/DifferenceMarkup (the diff will fail on input trees which already use that namespace).

ljdump reads the journal entries from a LiveJournal (or compatible) blog site and archives them in a subdirectory named after the journal name. Both the journal entries and journal comments are downloaded, which makes ljdump a great backup tool for creating offline copy of your journal. The program may be run as often as needed to bring the backup copy up to date. Both new and updated items are downloaded. ljdump uses only standard Python libraries, so it will work wherever Python itself does (Windows, Linux, FreeBSD, Mac OS X, etc).

Sphinx is a full-text search engine, distributed under GPL version 2. Commercial license is also available for embedded use. Generally, it's a standalone search engine, meant to provide fast, size-efficient and relevant fulltext search functions to other applications. Sphinx was specially designed to integrate well with SQL databases and scripting languages. Currently built-in data sources support fetching data either via direct connection to MySQL, or from an XML pipe. As for the name, Sphinx is an acronym which is officially decoded as SQL Phrase Index.

The functions optionaly exported by this module allows you to open URLs in the user browser. A set of known commands per OS-name is tested for presence, and the first one found is executed. With an optional parameter, all known commands are checked. The "open_browser" uses the system() function to execute the command. If you want more control, you can get the command with the "open_browser_cmd" or "open_browser_cmd_all" functions and then use whatever method you want to execute it.

This module prints per-component profiling information to STDERR (usually directed to the Apache error log). Its output looks like this: =Mason= 127.0.0.1 - /NoAuth/webrt.css BEGINS {{{ =Mason= 127.0.0.1 - /NoAuth/webrt.css {{{ =Mason= 127.0.0.1 - /Elements/Callback {{{ =Mason= 127.0.0.1 - /Elements/Callback }}} 0.0008 =Mason= 127.0.0.1 - /NoAuth/webrt.css }}} 0.0072 =Mason= 127.0.0.1 - /NoAuth/webrt.css }}} ENDS Each row contains five whitespace-separated fields: =Mason=, remote IP address, -, indented component name, and how many seconds did it take to process that component, including all subcomponents called by it. The beginning and end of the initial request is represented by the special time fields BEGINS and ENDS.

This module allows a Class::AlzaboWrapper::Cursor object to be used as a TT2 iterator. For a cursor which returns one object at a time, the iterator simply returns one object per iteration. When the cursor returns multiple objects, the iterator returns a hash reference where the keys are the table name of the object's class in lower-case, with camel-casing turned into underscores. The values of the hash are the objects. So if the cursor returns Foo::User and Foo::Page objects, the keys are "user" and "page".

encode and decode strings into and from application/x-www-form-urlencoded The application/x-www-form-urlencoded format encodes a ordered data sets of pairs consisting of a name and a value, with pairs separated by ampersand or semicolon and names and values separated by the equal sign. Space characters are replaced with plus sign and any characters not in the unreserved character set is encoded using the percent-encoding scheme also used for resource identifiers. A percent-encoded octet is encoded as a character triplet, consisting of the percent character "%" followed by the two hexadecimal digits representing that octet's numeric value.

PyMT is a simple Python module which allows you to easily connect to a Movable Type weblog, using it's built in XML-RPC API. PyMT is capable of handling every MT call available. This interface allows you to access most of the core functionality of Movable Type, including the ability to view, post, delete and edit weblog entries, fetch user information, apply categories to your posts and get information about trackback pings. Every XML-RPC method is accessed using a PyMT method with exactly the same name. PyMT is basically just a light wrapper, which hides the xml-rpc part of the work.

Pyramid is a small, fast, down-to-earth Python web application development framework. It is developed as part of the Pylons Project. The major feature additions in Pyramid 1.0 are: * New name and branding association with the Pylons Project. * BFG conversion script * Paster template improvements * Terminology changes * Better platform compatibility and support * Direct built-in support for the Mako templating language. * Built-in support for sessions. * Updated URL dispatch features * Better imperative extensibility * ZCML externalized * Better support for global template variables during rendering * View mappers * Testing system improvements * Authentication support improvements * Documentation improvements