so lets say my client has a requirement to build a website that consists of the usual CRUD and a few forms for registration and collecting some other details.
Is this accomplished easily without resorting to traditional frameworks? Not seeing it (please enlighten me) especially the drudgery of capturing form attributes and having them turn into java objects and then validating them. Rakesh On Mon, Nov 1, 2010 at 10:08 AM, Casper Bang <[email protected]> wrote: >> This has occasionally led us to keeping more than may be desired in a more >> general resource, for example say /customer/45 with a lot of data, rather >> than /customer/45, /customer/45/billingaddresses, /address/1, /address/2, >> /address/378 as separate resources, incurring 1+n calls to the server, 1+n >> transactions/auth checks etc. > > But don't you OTOH find it rather easy to add caching so that the > chattyness is isolated at the HTTP level, rather than reaching the > backend? Spreading short-lived self-populating caches at strategic > places seems to make all the difference with REST architectures. > > -- > You received this message because you are subscribed to the Google Groups > "The Java Posse" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/javaposse?hl=en. > > -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
