[tohu-users] Stateless/stateful servlet in Tohu

Mon Mar 1 04:50:42 EST 2010

oh right, yes of course. The agent config is based on URI, but there is one
knowledge session per HTTP session - so yes, that would be a problem. I
assumed you meant different http sessions. I guess it would be possibel to
have the knowledge session keyed on part of the URI as well for this (so
multiple rule sessions per http sessions, whereas now there is just one with
a fixed name).

On Sat, Feb 27, 2010 at 12:20 PM, Nicolas Martignole <
nicolas at touilleur-express.fr> wrote:

> Hi Damon, Hi Michael
>
> Thanks for your feedback.
>
> I'll try to see if it would be possible to enhance the Stateful Server so
> that 2 URLs are handled
> with 2 differents Agents.
>
> My use case is that 2 differents Portlets, in the same WAR, must be able to
> use 2 differents
> set of rules. And so far, as you explained, there's a single Questionnaire
> per HTTP Session.
>
> Not a big issue, we might be able to find a solution, based on the URI for
> instance.
>
> I'll try to see if I can adapt-it
> :-)
> Thanks
>
> Regards, Nicolas
>
> (yes, from Paris/France ;-) )
>
> 2010/2/27 Damon Horrell <Damon.Horrell at solnetsolutions.co.nz>
>
> I think the problem though is that there is only one session so when you
>> hit the second url, then nothing happens because you already have a session
>> established.  (The branching-example has 3 different agents and I had to
>> delete the knowledgeSession when switching between them otherwise I'm pretty
>> sure it just stayed with the original one.)
>>
>> In a portal environment, the different portlets almost need to behave like
>> different users.
>>
>> Currently Tohu only supports there being a single Questionnaire per
>> session, so we'd either have to enhance that so that there were two
>> independent ones within the session for each portlet, or change the
>> execution server so that each agent url has a different knowledgeSession
>> behind it (could this be a simple configuration option cos the current
>> behaviour is also useful).
>>
>> Another approach (which Nicholas could try) might be just to have a single
>> agent and a single Questionnaire for the whole application and write some
>> custom javascript so that each portlet only fetched the parts of the
>> Questionnaire that it should display (probably using Groups).  i.e. it would
>> be a bit like a 2-page Questionnaire but where each page was actually each
>> portlet.  I haven't really thought this through fully though so this might
>> not acually work easily.
>>
>> Damon
>>
>> -----Michael Neale <michael.neale at gmail.com> wrote: -----
>>
>> To: Damon Horrell <Damon.Horrell at solnetsolutions.co.nz>
>> From: Michael Neale <michael.neale at gmail.com>
>> Date: 02/27/2010 01:21PM
>> cc: Nicolas Martignole <nicolas at touilleur-express.fr>,
>> tohu-users at lists.jboss.org
>> Subject: Re: [tohu-users] Stateless/stateful servlet in Tohu
>>
>>
>> Yes different URLs should result in different agents being loaded (each
>> will have their own config, so there has to be a matching config file for " sample2".
>>
>>
>> There was some talk around stateless - the idea being that all
>> question/answer state is kept on the client and passed as needed (say in a
>> cookie) and this could work in theory for very small amounts of data.
>>
>> On Sat, Feb 27, 2010 at 10:50 AM, Damon Horrell < Damon.Horrell at solnetsolutions.co.nz
>> > wrote:
>>
>>> Hi Nicolas,
>>>
>>> It's good to see someone on the other side of the world using Tohu :-)
>>>
>>> Tohu requires that you use the stateful session because only changes are
>>> sent back and forth between the client and server, and so that state needs
>>> to be maintained on the server.  Stateless would be useful for a scenario
>>> where the rules are just doing some sort of one-off calculation based on the
>>> inputs provided.
>>>
>>> Michael will need to answer re whether the execution server is able to
>>> run 2 agents simultaneously and how to to that.  In the meantime, you could
>>> work around this problem by creating a separate war file for each and
>>> deploying them both to your app server.  I have had a number of Tohu
>>> applications running simultaneously this way, which is exactly what you need
>>> for use within a portal.
>>>
>>> Regards, Damon
>>>
>>>
>>> ----- tohu-users-bounces at lists.jboss.org wrote: -----
>>>
>>> To: tohu-users at lists.jboss.org
>>> From: Nicolas Martignole < nicolas at touilleur-express.fr >
>>> Sent by: tohu-users-bounces at lists.jboss.org
>>> Date: 02/27/2010 05:42AM
>>> Subject: [tohu-users] Stateless/stateful servlet in Tohu
>>>
>>>
>>> Hi Michael
>>>
>>> JBoss Tohu is really a great project. I worked on a Grails similar
>>> project
>>> few months ago, and I was really happy to discover Tohu later.
>>>
>>> My first question is about the Stateless/stateful URL and Servlet in Tohu
>>> implemented in Scala.
>>>
>>> I understood how to close a session with the URI and dispose-session
>>> in stateful mode. However, and because I'm a beginner with Scala,
>>> what are the main differences between the stateless and the stateful
>>> servlet
>>> in JBoss Tohu ?
>>>
>>> My Portlet has 2 view modes : normal and maximized. Each view mode
>>> is in fact a simple JSP. I oberved that if I use the stateful mode, and
>>> I try to load 2 separates context/scenarion (with /stateful/sample1 and
>>> /stateful/sample2)
>>> then the 2nd state is never loaded.
>>>
>>> I'd like to understand a little bit more this part of Tohu
>>>
>>> Thanks for your help, and for the great work
>>>
>>> Nicolas
>>>
>>>
>>> _______________________________________________
>>> tohu-users mailing list
>>> tohu-users at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/tohu-users
>>>
>>>
>>> Attention: This email may contain information intended for the sole use
>>> of the original recipient. Please respect this when sharing or disclosing
>>> this email's contents with any third party. If you believe you have received
>>> this email in error, please delete it and notify the sender or postmaster at solnetsolutions.co.nz
>>> as soon as possible. The content of this email does not necessarily
>>> reflect the views of Solnet Solutions Ltd.
>>> _______________________________________________
>>> tohu-users mailing list
>>> tohu-users at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/tohu-users
>>>
>>>
>>
>>
>> --
>> Michael D Neale
>> home: www.michaelneale.net
>> blog: michaelneale.blogspot.com
>>
>>
>> Attention: This email may contain information intended for the sole use of
>> the original recipient. Please respect this when sharing or disclosing this
>> email's contents with any third party. If you believe you have received this
>> email in error, please delete it and notify the sender or
>> postmaster at solnetsolutions.co.nz as soon as possible. The content of this
>> email does not necessarily reflect the views of Solnet Solutions Ltd.
>>
>> _______________________________________________
>> tohu-users mailing list
>> tohu-users at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/tohu-users
>>
>>
>
> _______________________________________________
> tohu-users mailing list
> tohu-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/tohu-users
>
>

-- 
Michael D Neale
home: www.michaelneale.net
blog: michaelneale.blogspot.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/tohu-users/attachments/20100301/e143ac62/attachment.html 