Restlet 1.1 M1 (Development branch)


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News Restlet 1.1 M1 (Development branch)
# 1  
Old 12-24-2007
Restlet 1.1 M1 (Development branch)

Restlet is a lightweight REST framework for Java. The project is composed of two parts, the Restlet API (alternative to Servlet API) and a reference implementation (Noelios Restlet Engine). It supports all REST concepts (resource, representation, data, connector, components, etc.) and is suitable for both client and server REST applications. The server connectors provided areHTTP(S), AJP (via Mortbay's Jetty or an adapter Servlet) and the client connectors are HTTP(S), File, JDBC, and SMTP(S).License: GNU General Public License (GPL)Changes:
Resource was refactored into a lower-level class(Handler) and higher-level methods were moreclearly defined. Many improvements were made tofacilitate the usage with Spring. Component'sinternal router was added to modularize largeapplications. RIAP scheme was added for optimizedinternal dispatching. Built-in HTTP client andserver connectors were added to NRE (BIO).Experimental Grizzly HTTP server (full NIO) wasadded. An experimental WADL extension was added toconfigure components. Representations can now beexposed via BIO Reader/Writer. A new JAXBextension was added for easy XML to POJO mappings.Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question
RT::Client::REST::SearchResult(3pm)			User Contributed Perl Documentation		       RT::Client::REST::SearchResult(3pm)

NAME
RT::Client::REST::SearchResult -- Search results representation. SYNOPSIS
my $iterator = $search->get_iterator; my $count = $iterator->count; while (defined(my $obj = &$iterator)) { # do something with the $obj } DESCRIPTION
This class is a representation of a search result. This is the type of the object you get back when you call method "search()" on RT::Client::REST::Object-derived objects. It makes it easy to iterate over results and find out just how many there are. METHODS
count Returns the number of search results. This number will always be the same unless you stick your fat dirty fingers into the object and abuse it. This number is not affected by calls to "get_iterator()". get_iterator Returns a reference to a subroutine which is used to iterate over the results. Evaluating it in scalar context, returns the next object or "undef" if all the results have already been iterated over. Note that for each object to be instantiated with correct values, retrieve() method is called on the object before returning it to the caller. Evaluating the subroutine reference in list context returns a list of all results fully instantiated. WARNING: this may be expensive, as each object is issued retrieve() method. Subsequent calls to the iterator result in empty list. You may safely mix calling the iterator in scalar and list context. For example: $iterator = $search->get_iterator; $first = &$iterator; $second = &$iterator; @the_rest = &$iterator; You can get as many iterators as you want -- they will not step on each other's toes. new You should not have to call it yourself, but just for the sake of completeness, here are the arguments: my $search = RT::Client::REST::SearchResult->new( ids => [1 .. 10], object => sub { # Yup, that's a closure. RT::Client::REST::Ticket->new( id => shift, rt => $rt, ); }, ); SEE ALSO
RT::Client::REST::Object, RT::Client::REST. AUTHOR
Dmitri Tikhonov <dtikhonov@yahoo.com> perl v5.14.2 2011-12-27 RT::Client::REST::SearchResult(3pm)