Slightly more complex demo

[hcientist]

In talking to different people about opencoweb as a coop/collab web app framework, I have seen that many people have in their minds a certain class of things when we say "app framework" they are looking for something like django or rails that implements MVC. So when looking at the applications (colist and coweb for example) there is a noticeable missing piece: persistence. It might be nice if there were an example that included some persistence, even if it's just authenticating against the db or something. The only concern in adding such an example would be that it might confuse people and make them think that coweb does indeed serve as an app framework that implements MVC...

my suggestion: some diagram of MVC that shows where in there opencoweb comes in, and then a example so that they could see how to pair opencoweb on the front with some other framework or custom implementation that serves for the other functionality needed by many web apps.

[vinomaster]

Mike:
Interesting that you brought this up. We are working on a sample demo that would allow for a common UI widget to operate with and without persistence. OpenCoweb will soon have a new server-side component called a moderator which handles session management.

We will keep this issue open until the code is done so that you can then review the variations of our CoTree sample.

CoTree is currently located at demodev.opencoweb.org; A version of this app with the use of the new moderator code on our Java Server will be coming soon.

[vinomaster]

Mike -- Take a look at this demo and associated tutorial. Let us know if this new server side persistence model addresses your concerns. If not, please elaborate on your requirements.

http://vhost1628.developer.ihost.com:8082/cotree/#/cowebkey/eda6e09431feef611b1e7df7bfb39042