A "session" is a dynamic, volatile object containing data that may be modified by rules.
You would not want to pass such an object across different applications. If you have a serialized knowledge base == a set of rules (+functions, declares) you can use it in any number of programs by deserializing the serialization so that the originally built and serialized knowledge base is recreated. Within one application program you can use a knowledge base to create any number of independet stateful/less knowledge sessions, in paralles, or one after the other. For a web application, you may have to create another knowledge session for each user request or connection. Alternatively, you can reuse knowledge sessions for one request after the other *provided* you can return the session to a "clean" initial state. You might maintain a session pool within a thread pool if you want to go that way. -W On 16 December 2011 10:04, srinivasasanda <[email protected]> wrote: > Hi manstis > > Across web applications same session object to be used > > -- > View this message in context: > http://drools.46999.n3.nabble.com/Can-we-make-our-kbase-object-available-from-one-context-to-another-context-one-application-to-anothe-tp3588689p3591107.html > Sent from the Drools: User forum mailing list archive at Nabble.com. > _______________________________________________ > rules-users mailing list > [email protected] > https://lists.jboss.org/mailman/listinfo/rules-users _______________________________________________ rules-users mailing list [email protected] https://lists.jboss.org/mailman/listinfo/rules-users
