Three Way Data Binding without Websockets

[jrief]

Three Way Data Binding without Websockets

[jrief]

By recycling the code from https://github.com/jrief/django-websocket-redis, this should be quite easy and doable using the key-value store from Redis without its message-queue.

However, in order to get a kind of intermediate responsivness, I always would go for a long polling service in case for some reason you can't run websockets.
Long polling services have the serious drawback in that they don't scale well, since each open GET request blocks one worker. In that case it would probably be better to use an asynchronous framework side by side with Django.

If that answered your question, please close this issue.

[cancan101]

My hope was to be able to have rudimentary three way binding using just django and angular without having to install redis or another process in the server.

[jrief]

In Angular you have a model and your scope. The scope is a POJO and Angular takes care to sync it with your model. If you want to have 3-way data-binding you need a third copy of that object on the server. How would you otherwise sync that data in an asynchronous environment? There is no free lunch for it, so I did it with Websockets and Redis.

[cancan101]

I guess my question is about the feasibility of offering a three data
binding using standard http polling as an alternative to installing redis.
On Jul 8, 2014 12:30 PM, "Jacob Rief" [email protected] wrote:

In Angular you have a model and your scope. The scope is a POJO and
Angular takes care to sync it with your model. If you want to have 3-way
data-binding you need a third copy of that object on the server. How would
you otherwise sync that data in an asynchronous environment? There is no
free lunch for it, so I did it with Websockets and Redis.

—
Reply to this email directly or view it on GitHub
#79 (comment).