Sponsored Content
Special Forums News, Links, Events and Announcements Software Releases - RSS News Granite Data Services 1.1.0 RC1 (Default branch) Post 302189401 by Linux Bot on Friday 25th of April 2008 04:10:08 PM
Old 04-25-2008
Granite Data Services 1.1.0 RC1 (Default branch)

Granite Data Services (GDS) is an alternative toAdobe LiveCycle (Flex 2) Data Services forJ2EE application servers. It is not, however, adrop-in replacement: you won't be able to simplydeploy a Flex 2 Data Services application into aGranite Data Services server without modifications. The main goal of this project is to provide a framework for Flex 2/EJB3/Spring/Seam/Guice/Pojo application development with full AMF3/RemoteObject benefits. It has a Data Push feature implemented as AMF3 requests sent over HTTP (Comet).License: GNU Lesser General Public License (LGPL)Changes:
This release brings many new features, improvements, and bugfixes: tighter Granite/JBossSeam integration (Tide), an improved ActionsScript3 generator (Gas3), a new ActionsScript3/Java type conversions stack, and (partially) automated configuration for several Flex/Granite options.Image

More...
 
Session::Flex(3)					User Contributed Perl Documentation					  Session::Flex(3)

NAME
Apache::Session::Flex - Specify everything at runtime SYNOPSIS
use Apache::Session::Flex; tie %hash, 'Apache::Session::Flex', $id, { Store => 'DB_File', Lock => 'Null', Generate => 'MD5', Serialize => 'Storable' }; # or tie %hash, 'Apache::Session::Flex', $id, { Store => 'Postgres', Lock => 'Null', Generate => 'MD5', Serialize => 'Base64' }; # you decide! DESCRIPTION
This module is an implementation of Apache::Session. Unlike other implementations, it allows you to specify the backing store, locking scheme, ID generator, and data serializer at runtime. You do this by passing arguments in the usual Apache::Session style (see SYNOPSIS). You may use any of the modules included in this distribution, or a module of your own making. If you wish to use a module of your own making, you should make sure that it is available under the Apache::Session package namespace. USAGE
You pass the modules you want to use as arguments to the constructor. The Apache::Session::Whatever part is appended for you: you should not supply it. For example, if you wanted to use MySQL as the backing store, you should give the argument "Store =" 'MySQL'>, and not "Store =" 'Apache::Session::Store::MySQL'>. There are four modules that you need to specify. Store is the backing store to use. Lock is the locking scheme. Generate is the ID generation module. Serialize is the data serialization module. There are many modules included in this distribution. For each role, they are: Store: MySQL Postgres DB_File File Lock: Null MySQL Semaphore Generate: MD5 Serialize: Storable Base64 UUEncode In addition to the arguments needed by this module, you must provide whatever arguments are expected by the backing store and lock manager that you are using. Please see the documentation for those modules. AUTHOR
This module was written by Jeffrey William Baker <jwbaker@acm.org>. SEE ALSO
Apache::Session::File, Apache::Session::DB_File, Apache::Session::MySQL, Apache::Session::Postgres, Apache::Session perl v5.12.1 2007-09-28 Session::Flex(3)
All times are GMT -4. The time now is 06:33 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy