Article Discussion
Scaling with Rich Clients
Summary: Rich clients can not only provide more interactive, desktop-like, user interaction, but also have the ability to cache significant amounts of application data on the client and perform processing on that data. In this interview with Artima, Xoetrope CTO Val Cassidy explains how client-side data processing can help scale an enterprise application.
4 posts on 1 page.      
« Previous 1 Next »
The ability to add new comments in this discussion is temporarily disabled.
Most recent reply: July 6, 2007 8:32 AM by Bill
Frank
Posts: 135 / Nickname: fsommers / Registered: January 19, 2002 7:24 AM
Scaling with Rich Clients
July 5, 2007 10:00 AM      
In this interview with Artima, Xoetrope CTO Val Cassidy explains how client-side data processing can help scale an enterprise application:

http://www.artima.com/lejava/articles/javaone_2007_val_cassidy.html

What do you think of Xoetrope's client-side caching approach to scaling an enterprise applications?
Achilleas
Posts: 98 / Nickname: achilleas / Registered: February 3, 2005 2:57 AM
Re: Scaling with Rich Clients
July 6, 2007 1:36 AM      
Is the link correct? All I get is an 'articles from null' empty page.
vin
Posts: 1 / Nickname: vineetraja / Registered: February 19, 2007 1:16 PM
Too Poor to Scale
July 6, 2007 4:18 AM      
The link Leads to a page which sadly states
"Article Null!"

Perhaps this is the irony of scaling with rich clients!
Bill
Posts: 408 / Nickname: bv / Registered: January 17, 2002 4:28 PM
Re: Too Poor to Scale
July 6, 2007 8:32 AM      
> The link Leads to a page which sadly states
> "Article Null!"
>
> Perhaps this is the irony of scaling with rich clients!

No, it was my fault. I added a redirect to Apache last night that was intended to just redirect exactly the /lejava/articles URL, but it ended up redirecting /lejava/articles*, and I didn't notice until I saw these messages. It's an example of something I've noticed over the years, which is that most of the problems on the live site have to do with configuration, not things that would have been caught by unit testing the code. Anyway, sorry about the problem. It is fixed now.
4 posts on 1 page.
« Previous 1 Next »