Hi Sébastien,
thanks to the database routing system and the possibility add any backend
database (or data source, however you wanna call it) directly into broke, or
your project.
You can think of it as a sort of plugin system that anyone can use.
For instance, if you are using django-piston or django-tastypie to create a
nice public API, you can create a db backend to match your public api, however
you wanna create it.
Using the models you can do stuff like:
MyModel.objects.filter({ id__gte: 10 }).using('nodejs-remote-backend').all()
and you get all the data you want from that db backend or you can use a db
router to make sure all the requests for that model are redirected to that
specific db backend.
Thanks for the support :)
Davide
Il giorno 05/apr/2012, alle ore 10:42, sebastien piquemal ha scritto:
> I guess the people that don't get the point have probably never made a heavy
> Javascript application ... Ever used Backbone.js ?
>
> client-side - one page - websites are much nicer to use than any website with
> a page load after every click.
>
> So I totally understand why you would do such a project, and I actually think
> it is a lovely idea !!! On the other hand, I've started to think lately that
> Django is not the best backend solution for building such applicatons.
> So, @davide, how do you plan on making sure that any weird API can be
> plugged-in to the system ... will you separate nicely the model layer from
> the "backend" (web API, or dummy data store, or whatever) ???
>
> Cheers anyway, and I'll follow the project !
>
> Sébastien
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
