From: aurelien.dehay@... (=?iso-8859-15?q?Aur=E9lien?= DEHAY)
Date: 2003-01-16T00:58:52+09:00
Subject: Re: [ANN] Radical 0.6

Idan Sofer <idan@idanso.dyndns.org> writes:

> Aur�lien DEHAY wrote:
>
>>Hello.
>>  
>>
> Hello and thank you for the feedback:)

'Welcome. I think I will have a lot of questions these days :)

>
>>We plan to use Radical (or at least Ruby) for a project. Looking at
>>Radical, it doesn't seems bad at all, but I wonder if there is a way
>>to make a persistant handler instance.
>>
> Please explain what do you mean by "persistent handler instance"?

Excactly what you explain later in fact: a instance of a class.

>
> A handler can be either be a class(in the case a new instance is created 
> for each incoming request), or be given as an instance of a class(In 
> this case the same instance is used for all the requests), and it main 
> duty is to process the HTTP requests, so it's role is similiar to that 
> of of a servlet.

Ok. The term "persistant" is not the good one. I mean "persistant
across the lifetime of the server".

In fact, we want to write a webboard in ruby. So we need to have a
class which manage the messages (with database connection or not), and
some classes to generate the backends (HTML, XML, WML) for the
clients. So, to have a correct management for the messages, I need to
have only one instance of this classe for the site.

I wonder how put this classes in the Radical architecture. The backend
management would be done with handlers, but for the messages
management?


> So, the question arises, how can persistence can be used in this
> case?
>
>>In fact, we would like to make some things like EJB: a server side
>>instance of an object, and severals web pages, templates, etc. using
>>it.
>>
> That's an interesting idea...
>
>
> Idan

-- 
Aurelien