Shared state

[itte]

Hey,

I'm considering to use flapjax for a project but I have a question
about it.
I read a few times that flapjax has "Access-control for shared data".
Does that means flapjax allows a kind of way to lock server saved
objects when 2 users
are trying to read/write to it at the same time? Since if flapjax has
support for that it would be
a perfect candidate for my project. However.. I don't really find info
in the tutorial or docs on how
to do this. Could someone give any pointers on this?

Thanks,
itte

[Jay Shepherd]

HI itte

Flapjax is client side and you would typically implement your own server side persistence.
You can do that in all sorts of ways, ive been using PHP

--
Flapjax home page: www.flapjax-lang.org
Flapjax list: groups.google.com/group/flapjax
Post: fla...@googlegroups.com
Unsubscribe: flapjax-u...@googlegroups.com

[Leo Meyerovich]

Hi,

The server was experimental. I recommend building your own object store, say on top of a nosql db w/ memcached (it shouldn't be too bad using node.js and common libraries). Each persistent object had an associated access control list. We weren't using the lists for ordering concurrent access but 1) preventing data confidentiality and integrity violations while 2) providing an easy reactive API for sharing and persistence.

Revisiting this issue, say by incorporating something like membranes (or our recent work with 'object views') for better sharing and focusing on the distributed DB nature of phones+nature would make writing phone apps much more palatable. I was recently in a position where I saw 5-6 teams roll their own secure distributed objects for Android/iOS/web views and it was a disaster.