Podius 5.2.0 (Default branch)


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News Podius 5.2.0 (Default branch)
# 1  
Old 12-25-2007
Podius 5.2.0 (Default branch)

Image Podius is a flexible content management system that simplifies building of dynamic Web sites by providing clean ways to create, manage, and publish all kinds of complex content. It offers command-line and Web-based interfaces, and features an intuitive object model on top of a file-based or RDBMS-based persistence layer. License: GNU General Public License (GPL) Changes:
Component search was implemented using a new SQL-like syntax. A dozen new rich property types were added, including Rating, ScalableImage, Country, and Currency. The existing administration scripts were enhanced (all have --help) and new scripts were added for finding, traversing, cloning, and destroying components from the command line. WikiText was integrated using a new property type. A more useful sample model using the new Page component type was included. Improvements were made in template functionality and new built-in functions. A better translation infrastructure was provided along with a number of useful Perl modules and scripts to aid development.Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question
Jifty::CAS(3pm) 					User Contributed Perl Documentation					   Jifty::CAS(3pm)

NAME
Jifty::CAS - Jifty's Content-Addressable Storage facility SYNOPSIS
my $key = Jifty::CAS->publish('js' => 'all', $content, { hash_with => $content, # default behaviour content_type => 'application/x-javascript', }); $ie_key = Jifty::CAS->publish('js' => 'ie-only', $ie_content, { hash_with => $ie_content, content_type => 'application/x-javascript', }); $key = Jifty::CAS->key('js', 'ie-only'); my $blob = Jifty::CAS->retrieve('js', $key); DESCRIPTION
Provides an in-memory "md5"-addressed content store. Content is stored under a "domain", and can be addressed using wither the "key", which is an "md5" sum, or the "name", which simply stores the most recent key provided with that name. BACKENDS
The default data store is an per-process, in-memory store. A memcached backed store is also available and has the benefits of sharing the cache across all instances of a Jifty app using Jifty::CAS. The memcached store is limited to objects less than 1MB in size, however. METHODS
publish DOMAIN NAME CONTENT METADATA Publishes the given "CONTENT" at the address "DOMAIN" and "NAME". "METADATA" is an arbitrary hash; see Jifty::CAS::Blob for more. Returns the key on success, or undef on failure. key DOMAIN NAME Returns the most recent key for the given pair of "DOMAIN" and "NAME", or undef if none such exists. retrieve DOMAIN KEY Returns a Jifty::CAS::Blob for the given pair of "DOMAIN" and "KEY", or undef if none such exists. serve_by_name DOMAIN NAME REQUESTED_KEY Intelligently serves up the content of the object at NAME (not REQUESTED_KEY) in DOMAIN. REQUESTED_KEY is currently used only to check if the content at NAME equals the content requested. If so, this method responds with an HTTP 304 status, indicating the content hasn't changed. This use case assumes that content is served to clients from the CAS with the CAS key (an MD5 sum) as the filename or part of it. The "content_type" key in the requested object's metadata is expected to be set and is used for the HTTP response. This method is usually called from a dispatcher rule. Returns the HTTP status code set by this method (possibly for your use in the dispatcher). perl v5.14.2 2010-09-25 Jifty::CAS(3pm)