16. Users want fast & smooth SaaS apps
Users want multiplateform SaaS apps
Users want dynamic & interactive SaaS apps
You should do so!
app.wisembly.com/sflive
17. Users want fast & smooth SaaS apps
Users want multiplateform SaaS apps
Users want dynamic & interactive SaaS apps
W ?
You shouldO so!
do
T H
B U
app.wisembly.com/sflive
36. MUST READ
http://fr.slideshare.net/nachomartin/symfony-
javascript-combining-the-best-of-two-worlds
app.wisembly.com/sflive
37. ar tin
nacm
@
Books = new
Backbone.collection();
Books.url = ‘/books’;
app.wisembly.com/sflive
38. ar tin
nacm
@
Books = new
Backbone.collection();
Books.url = ‘/books’;
Books.fetch();
GET /books
app.wisembly.com/sflive
39. ar tin
nacm
@
events:
{ ‘click
.mybutton’:‘doStuffAndSave’ }
doStuffAndSave: function() {
var book = Books.get(3);
book.stuff();
book.save();
}
app.wisembly.com/sflive
40. ar tin
nacm
@
events:
{ ‘click
.mybutton’:‘doStuffAndSave’ }
doStuffAndSave: function() {
var book = Books.get(3);
book.stuff();
book.save();
}
PUT /books/3
app.wisembly.com/sflive
86. Push «surprises»
• Must find always opened port
app.wisembly.com/sflive
87. Push «surprises»
• Must find always opened port
• Websocket protocol must go through firewalls
app.wisembly.com/sflive
88. Push «surprises»
• Must find always opened port
• Websocket protocol must go through firewalls
• Push may disconnect (very!) frequently and loose
events (duh!)
app.wisembly.com/sflive
90. • 80 always opened, but websocket very
often blocked -> FAIL -> goto 443 w/ https
app.wisembly.com/sflive
91. • 80 always opened, but websocket very
often blocked -> FAIL -> goto 443 w/ https
• Implement disconnection mechanism and
lost events in case of socket.io «degraded»
protocol (xhr polling, jsonp polling)
app.wisembly.com/sflive