search

ianhaggerty / backbone-sails

A plugin for Backbone that makes integrating with Sails JS easier. Both leverage a model-view architecture, it's only natural to have them talk to each other.
MIT License
7 stars 1 forks source link

Sails V11 #6

Open dottodot opened 9 years ago

dottodot commented 9 years ago

Just out of curiosity will this be compatible with sails v11 or will some work be required on that?

ianhaggerty commented 9 years ago

Currently working on it :)

Lot of new features with this release, all quite game breaking for Backbone.Sails!

Stick to sails 0.10 & sails.io 0.9 for Backbone.Sails v0.1

dottodot commented 9 years ago

Hi, just wondering if you were still planning on updating this to work with v11 as I need to use v11 on a project so need to make a decision on if it's going to be possible to use this.

ianhaggerty commented 9 years ago

Have reviewed code & revisited Sails. I'm afraid I won't continuing this project for now. I've simply gone off Sails altogether. Thanks for your interest though.

hardchor commented 9 years ago

@oscarhaggerty just out of interest, are you using any alternative real-time framework?

dottodot commented 9 years ago

Shame but no worries.

ianhaggerty commented 9 years ago

Not at the moment. Playing around with Koa & enjoying what I see.

In principle, it wouldn't be too difficult to write a back-end which provides a service that Backbone.Sails requires. This project is half way to a 'standard interface' for real-time persistence (much like the REST convention for stateless persistence). In that sense, the server-side framework and the front-end client are merely implementers a real-time communication protocol.

Sails is just a little too pragmatic, favouring efficiency over elegance, to continue this idea (if that makes any sense).

ianhaggerty commented 9 years ago

It is likely I will be migrating this project to a different back-end. I am pretty **set on Koa along with Bookshelf (a backbone inspired relational ORM), along with co for some generator goodness :).

**For a first implementation. My main aim is to nail down a standard for a "resourceful pub/sub" (need a new name for that) that is independent of the front or back end, and then go from there.