+1, its a complete myth as well that app servers didn't retain state, they did and pretty much always in the database.
Every interaction pretty much is stateful in someway, its either a request for state or a request to change state in someway. After all if there is no information or no result from interaction... why bother? Steve On 05/01/07, Stefan Tilkov <[EMAIL PROTECTED]> wrote:
On Jan 5, 2007, at 7:05 PM, Gervas Douglas wrote: > O'Toole: There's a particular new challenge in clustering that we have > to deal with in SOA. In the Web tier when we scale up app servers, we > basically did stateless clustering with occasionally state involved. > There were a couple of techniques we had to learn, but we figured that > out. We needed to use load balancers and we got that to work pretty > well. The challenge with SOA is the type of applications that people > are building are stateful. Because what people are using SOA to do is > model business processes, which by definition are stateful things. So > this is a much more complicated level of clustering than simple IP > load balancing that we did with app servers. This seems a non sequitur to me. Statefulness of business processes does not imply stateful communication. Stefan -- Stefan Tilkov, http://www.innoq.com/blog/st/
