Free microsoft access standalone application software for linux

REST::Application is a framework for building RESTful web-applications.

SYNOPSIS

# MyRESTApp L instance / mod_perl handler
package MyRESTApp;
use Apache;
use Apache::Constants qw(:common);

sub handler {
__PACKAGE__->new(request => $r)->run();
return OK;
}

sub getMatchText { return Apache->uri }

sub setup {
my $self = shift;
$self->resourceHooks(
qr{/rest/parts/(d+)} => get_part,
# ... other handlers here ...
);
}

sub get_part {
my ($self, $part_num) = @_;
# Business logic to retrieve part num
}

# Apache conf
< Location /rest >
perl-script .cgi
PerlHandler MyRESTApp
< /Location >

This module acts as a base class for applications which implement a RESTful interface. When an HTTP request is received some dispatching logic in REST::Application is invoked, calling different handlers based on what the kind of HTTP request it was (i.e. GET, PUT, etc) and what resource it was trying to access. This module wont ensure that your API is RESTful but hopefully it will aid in developing a REST API.

SOPE Application Server is an extensive set of frameworks (16 frameworks, ~1500 classes) which form a complete Web application server environment.
Besides the Apple WebObjects compatible appserver extended with Zope concepts, it contains a large set of reusable classes: XML processing (SAX2, DOM, XML-RPC), MIME/IMAP4 processing, LDAP connectivity, RDBMS connectivity, and iCalendar parsing.
The individual frameworks of the package can be used standalone (for example in Cocoa applications) and do not require the application server itself.
For MacOSX developers, the package includes SOPE:X, which contains special Xcode and Cocoa support for SOPE.
Enhancements:
- This release fixes a set of minor bugs.
- It improves the vCard parser, the IMAP4 client library, the MySQL adaptor, and BSD packaging.

PHP Generic Access Control List is a PHP class that offers Web developers a simple, yet immensely powerful "drop in" permission system for their current Web-based applications.
Main features:
- Split into two classes, and a seperate administration interface.
1. GACL class: Designed to be very small (517 lines of code including comments) and very fast, this class strictly takes care of the permission checks.
2. GACL_API class: Designed to be robust and flexible, this class takes care of creating/editing/deleting objects, groups and ACLs.
3. phpGACL Administration Interface: A set of scripts that allow for the easy administration of the entire GACL universe using only your browser.
- NOT limited to typical "read/write/execute" permissions similar to some flavours of *nix
- User definable "Access Control Objects" (ACO). These are objects which control what access is available to "requesters" (see below).
- Several examples:
- Enable - Projects
- View - Projects, View Own - Projects
- Edit - Projects, Edit Own - Projects
- Delete - Projects, Delete Own - Projects, UnDelete - Projects, UnDelete Own - Projects
- Add - Projects
- System down for Maintenance
- View - The letter "e" ;)
- User definable "Access Request Objects" (ARO). These are objects which request access from an "Access Control Object" (above) examples would be:
- Users/Accounts
- IP Addresses
- Browsers/Browser capabilities (JS/Flash/DHTML)
- User definable "Access eXtension Objects" (AXO). These are objects which extend permissions to a 3rd layer, optionally allowing you to set fine grained permissions on each individual item in your application, or even row in your database. AXOs are often used in cases where you only want to give a user access to a specific project or contact.
- Several examples:
- Projects - Project ID: 3474 (Accounting Software)
- Projects - Project ID: 3484 (Financial Software)
- Contacts - Contact ID: 4775 John Doe
- Contacts - Contact ID: 4795 John Doe
- Tree based ARO/AXO Object grouping with inheritance.
- Contains functionality to easily program add-ons. Examples would be for product pricing, or quantity limitations.
- One function application integration: acl_check()
- Simply pass this function four parameters, it doesnt get any easier!
- Supports the most popular databases using the ADODB database abstraction layer. (MySQL, PostgreSQL, Oracle, MSSQL)
- Complete web based administration interface.
- Scalable. A real-world working version with many added layers of complexity supports over 60,000 Accounts, 200 Groups and 300 ACOs.
Requierments:
- PHP 4.x or greater
- SQL database. (MySQL 3x/4.0.15+, PostgreSQL 7.2+, Oracle 9i+, MS-SQL 2000+)
Enhancements:
- This release contains several minor bugfixes and a fix for a major bug with del_object(), which caused transactions to abort prematurely.
- It also contains a slightly improved installer with Informix support, less possibility of conflicting code with other applications, and upgraded ADODB and Smarty packages.

1060 NetKernel is a resource oriented microkernel and application server that provides a coherent execution abstraction that radically reduces software complexity. Its self-consistent design is based on the convergence and unification of powerful fundamental concepts found in the World Wide Web and Unix.
Resource Oriented Microkernel
The heart of NetKernel is a high-performance, carefully designed, and tightly crafted microkernel. Services and resources within NetKernel are located by URI addresses, just as resources are located on the World Wide Web. NetKernel implements and extends REST 1 into a general-purpose processing abstraction and allows it to be applied to the finest granularity of software systems to achieve phenominal performance; just as the REST Web-architecture achieves global scaling and high performance.
Coherent Abstraction
NetKernel unifies code execution and resource identification into a single addressing and processing abstraction. With this, software development becomes a process of construction (coding services), composition (linking and issuing service and resource requests), and constraint (restricting data values and honoring boundaries).
The simplicity of URI identified resources means that the results of service calls can be cached just as other resources, resulting in self-optimizing software where computation cost is a guaranteed minima.
Reduce Software Complexity
The unification of resources and services with URI addressing radically reduces sofware complexity. Because resources are addressed by URI and each request is a Web-like REST request dispatched to the microkernel, binding between clients and services occurs dynamically for each request. This late binding and the indirection of logical URI addressing results in a loosely coupled system which may be easily adapted. In fact, NetKernel supports dynamic upgrading of software and can support multiple versions of the same components simultaneously.
Complexity brought about by system growth is also managed through the URI address space which may be remodelled and extended indefinitely. A complex aggregation of services may always be abstracted into one or more higher-level services surfaced through URI interfaces.
Main features:
Manage Complexity
- NetKernels unification of resource and service addressing through the active URI scheme combined with late binding and loose typing means that complex systems can be partitioned not just into smaller coorperating systems, you can now create micro-services that hide complexity.
- With NetKernel, design and build larger and more ambitious systems while maintaining control of complexity.
Process XML with ease!
- Processing XML is often just too difficult. But the potential of XML is communication with almost no limit. How to harness and leverage the potential of XML? NetKernel provides hundreds of XML technologies as simple services (no APIs). Simply compose XML services into powerful message processes...
Integrate diverse technologies, apply business logic
- NetKernels uniform URI addressing of resources and service allow you to encapsulate and hide the complexities of any technology, whether it is a Java API, legacy code, or remote corporate systems. Once encapsulated, develop new coordination logic in one of NetKernels scripting languages.
Transport technology independence
- Write a service or application and deploy it to service requests from multiple transports concurrently. NetKernel makes it easy to utilize SOAP 1.1, SOAP 1.2, HTTP, JMS, Email, and Cron.
Extreme performance from intra-application caching
- NetKernels fine-grained dependency cache transparently and opportunistically caches the results of all micro-service requests. NetKernel processes are self-optimizing with guaranteed minimal processing required for a given transaction.
Team Player
- NetKernel has several deployment options that allow it to play well with other technologies and systems. Deploy NetKernel as an advanced standalone application server, as an embedded "co-processor" within existing J2EE applications, as a JMS message processor, as a SOAP client or server, or as an embedded component within any application.
Enhancements:
- New features include support for Berkeley DBXML and PiNKY, a community developed module providing Yahoo! Pipes features.
- Updates include Groovy language support at release 1.0, Ruby (JRuby) support at 0.9.9, and XML library updates.
- There are also documentation updates and UI refinements.

Access Stats provides a script that enables you to keep track of activities on your web site.

Access Stats allows you to keep track of activities on your web site.

It extracts some statistic from a log file generated by log.pl.

These reports are generated by Access Stats:

- Visits by day
- Visits by hour
- Visits by week-day
- Referer
- Browser
- Operating System
- Countries
- Hostnames

PHP Database Access Through Arrays project can be used to access data stored in MySQL tables like accessing arrays. It uses SPL to implement several classes and iterators interfaces to access MySQL databases.

Examples:

$DB[test_table][] = array(
name => first,
value => the first row
);

foreach ($DB[test_table] as $i => $row) {
...
}

$DB[test_table][first][value] = 1st;

unset($DB[test_table][first]);

CGI::Application::Plugin::RateLimit is a plugin for CGI::Application which provides protection against a user calling a runmode too frequently. A typical use-case might be a contact form that sends email.

Youd like to allow your users to send you messages, but thousands of messages from a single user in a short period of time would be a problem.

Installation:

To install this module type the following:

perl Makefile.PL
make
make test
make install