[srm-cvs] CVS Update: - Adding OSCON proposal

Date: Sat Jun 22 21:58:36 CEST 2002
User: Derick Rethans
Directory: srmdoc

Log Message:
 [0.25]
 - Adding OSCON proposal
 
Added files:
           srmdoc/proposal-oscon (new version: 1.1)

[FILE: /srmdoc/proposal-oscon]

Derick
Rethans

JDI Media Solutions
H.v.Tussenbroekstraat 1
Dieren
GLD
6952 BL
The Netherlands
+31 6 505 702 45

d.rethans@jdimedia.nl

http://

Biography:
Derick Rethans provides solutions for internet related problems.
Working in his own company, he has acquired vast experience with PHP related
projects. He has contributed in a number of ways to the PHP project, including
the mcrypt extension, bugfixes, additions and support of the QA team. In
his spare time he likes to work on SRM: Script Running Machine, watch
movies and travel.

Title: Using SRM: Script Running Magic as a framework to enhance
persistency and automation of PHP objects.

Duration: 3 hour tutorial
Audience level: General

Audience Type:
Web Application developers

Preferred Date:
July 22-26, 2002

Abstract (max 250 words):
In this tutorial I will cover the problems or lacks in functionality
that currently exist in PHP with regard to persistency and automation.
After mentioning the problems that are currently present concerning the
lack of persistent objects and resource pooling, e.g. with database
connections, I will cover some of the solutions that are now
commonly in use to overcome these problems. After these introductary
topics I will go on to describe the application of SRM to provide solutions
to the lack of persistency of objects and resources. These solutions will
be demonstrated using two real-life examples. The first will go in depth into
a solution in which SRM is used to maintain a pool of connections and
the state of an application. The logic is written in PHP Objects, which
live on the SRM server. The second example will introduce the
architecture of a system in which objects are automated. These objects
interact with each other without any interference from the client side.
The client is used only to give input to the system and display the
state of the system.
Both examples will show an implementation of logic that differs from a
'normal' application implemented in PHP; all business logic is
implemented in persistent objects that maintain state and run in the
daemon.

Brief description (max 50 words):
In this tutorial session I will present a number of methods using SRM:
Script Running Machine as a tool to build an application around
persistent objects. These objects live inside the SRM daemon and
maintain state during a session or even throughout the lifetime of an
application. I will also cover resource management, and automation within
and interaction between so-called Banana application objects.
Received on Sat Jun 22 22:45:45 2002