[rules-users] Stateless vs Stateful

[Mauricio Salatino]

Hi Rob,
Just for you to know in the back a stateless session contains a Stateful
session. The stateless session reduce the number of things that you can do
against it. Allowing you to call just the execute method and automatically
disposing the session.
In the end you will not get any performance implication choosing one over
the other.

Cheers

2011/8/24 Rob Fisher <rob.fisher.l2gk at statefarm.com>

>  We have a batch application that will have 50 – 60 rule sets, comprised
> of 5 – 75 rules each.  We’ll run a group of individuals through the rules
> and potentially qualify them for various awards.   We’ll insert 10 facts,
> each containing a unique set of attributes which will be used in the rule
> sets to determine potential qualification.  The batch process will insert
> one individual’s data (10 facts) at a time, fire the rules, and return the
> results.  The data on the objects inserted will remain static.
>
> Also, in the future, we’d like to integrate the rule sets with a ‘what if’
> web application, wherein the individual can modify the input data, fire the
> rules, and see the results.
>
> Given this, can you recommend whether a Stateful or Stateless knowledge
> session is more appropriate than the other?  Is one more appropriate for a
> batch vs online application?
>
> Thanks
> Rob
>
>
>
>
> _______________________________________________
> rules-users mailing list
> rules-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/rules-users
>
>


-- 
 - CTO @ http://www.plugtree.com
 - MyJourney @ http://salaboy.wordpress.com
- Co-Founder @ http://www.jugargentina.org
 - Co-Founder @ http://www.jbug.com.ar

 - Salatino "Salaboy" Mauricio -
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/rules-users/attachments/20110824/2c1049d1/attachment.html