On Monday 31 July 2006 01:57, Barry Beattie wrote:
you're saying that, if you don't need syncronised data or being able
to pust data or messages to clients, then the garden variety remoting
would do just fine...
Yup.
so the opposite is true? if you *have* to have data in sync/ only one
copy
(I don't think even FDS gives you record locking
agreed - from my understanding (keen interest but no experiance in
battle...yet).
Where FDS would have failed us last year (if we could have used it)
would be when a particular record could be in multiple models at the
same time, either with
On Monday 31 July 2006 12:12, Barry Beattie wrote:
exellent front end to, say, Hibernate (hence my interest in hearing
CFHibernate may be a goer yet...). for sure I'll be keeping an eye out
for someone giving FDS + hibernate a good shake
:nods
I believe there is non-CF based FDS+hibernate
Tom, just to check...
you're saying that, if you don't need syncronised data or being able
to pust data or messages to clients, then the garden variety remoting
would do just fine...
yes?
so the opposite is true? if you *have* to have data in sync/ only one
copy of the record can be edited at
Hank,
Quick answer;
I think the Front Controller + Command (service to worker microarchitecture) is
still critical to the scalabilty and maintainability of your applications;
there's still value in model information being held on the model locator, but
FDS means that you don't need the
On Friday 28 July 2006 11:33, hank williams wrote:
there is value to cairngorm if I am using DataServices. Because it
seems to me data services already handles all changes to the model.
You just change the model and your changes are propagated
automatically to the server, and any other changes
6 matches
Mail list logo
