You get the idea!
Now you are available to run on Local and Remote  (using mina, I hope in less than a month we support hornetQ as well) and also DIstributed nodes (Rio).
Allowing you to start using Local for your testing and initial development (following some of my rules about remote/distributed environments, I will post some about this today or tomorrow on my blog) and then move the Remote or Distributed.

Greetings! :)

On Mon, Aug 16, 2010 at 11:36 PM, Tan Hui Onn <huionn@gmail.com> wrote:
Thanks for your reply. It clears my doubt : )

I checked your Drools Grid (Part 3) and found that it actually
supports Local Execution Node.
I like its 'transparency' so I can choose to use it later on with
minimal change in codes.

Thanks.

2010/8/16 Mauricio Salatino <salaboy@gmail.com>:
> If you don't want session fail over it will work out of the box. If you want
> to start a flow inside one node and then continue the process from another
> node it will work. Of course both nodes need to have a connection to the
> same database.
> The idea with Drools Grid is to simplify the deployment and distribution of
> your knowledge session across the grid and also do that transparently for
> your application :)
> Greetings.
>
> On Mon, Aug 16, 2010 at 2:20 AM, Tan Hui Onn <huionn@gmail.com> wrote:
>>
>> Some additional note to my question. The intended clustering need not
>> to support session failover. In other words, the session states will
>> not be replicated from one server to another.
>>
>> On Fri, Aug 13, 2010 at 8:36 PM, cafebabe <huionn@gmail.com> wrote:
>> >
>> > Hi,
>> > Based on my understanding from reading some drools posts and blogs,
>> > stateful
>> > knowledge session will not work correctly if drools is embedded into an
>> > application deployed in clustered application servers. Am I right?
>> >
>> > What if I want to use embedded drools purely for its BPM (drools flow)
>> > in
>> > clustered application? Any gotchas to take note or it will simply not
>> > working?
>> >
>> > anybody has related experience?
>> >
>> > (i found there is work-in-progress alternative - drools grid. but i
>> > prefer
>> > to start with embedded drools flow bcoz it is simpler to code and offers
>> > more control.)
>> > --
>> > View this message in context:
>> > http://drools-java-rules-engine.46999.n3.nabble.com/Embedded-Drools-into-clustered-application-tp1131520p1131520.html
>> > Sent from the Drools - User mailing list archive at Nabble.com.
>> > _______________________________________________
>> > rules-users mailing list
>> > rules-users@lists.jboss.org
>> > https://lists.jboss.org/mailman/listinfo/rules-users
>> >
>> _______________________________________________
>> rules-users mailing list
>> rules-users@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.jbug.com.ar
>
>  - Salatino "Salaboy" Mauricio -
>
> _______________________________________________
> rules-users mailing list
> rules-users@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/rules-users
>
>

_______________________________________________
rules-users mailing list
rules-users@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.jbug.com.ar
 
 - Salatino "Salaboy" Mauricio -