• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

DWR on the server-side

 
Ranch Hand
Posts: 948
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I am curious about the realities and best practices of the server side of DWR. I have scanned through examples on the web and most just show a simple POJO with some simple methods. That sounds great but how does that scale on the server side? What types of middle ware technology are people using with DWR? EJB? Spring?

- Brent
 
Ranch Hand
Posts: 136
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
My experience indicates POJOs scale very well. And I mean, why wouldn't they? So long as you're not oblivious to thread safety concerns, it should be fine.

Now, I've also used Spring with DWR, and I'm frankly not sure I like it more or less just yet. In some ways it's certainly nice (things like getting DataSource's in an object automatically is nice), but other things aren't (POJOs and DWR annotations means no config files, no extra "stuff" to think about). So I'm not passing judgement either way on that.

It all comes down I think to how you architect your application at a high level. If your client is doing most of the work, using the server, via DWR, as a service layer, which means you're using session sparringly, and you don't especially care about distributed execution where EJBs might actually make some sense (against what I believe to be typically true), then DWR with POJOs seems to be just the ticket.

If you have more specific concerns though I'd definitely be interested to hear them... I may be able to quell your fears a little, as it were, but you also might point out something I haven't thought of, which I'd appreciate for sure!
 
reply
    Bookmark Topic Watch Topic
  • New Topic