convore.json/groups/node/rest-vs-other-approaches-for-real-time-apps/messages.json

[{"user_id": 22875, "stars": [], "topic_id": 21286, "date_created": 1303765185.336272, "message": "Do you think it still makes sense to talk to a node.js backend with a REST approach, for real-time single-page apps? Or a more integrated approach, just passing JSON messages (or even something like now.js) to the server without specifying resources via URL.", "group_id": 1020, "id": 807299}, {"user_id": 1, "stars": [{"date_created": 1303767434.6365249, "user_id": 1175}], "topic_id": 21286, "date_created": 1303765563.1736729, "message": "If I were using node.js, I'd probably use socket.io because it does such a nice abstraction for you.", "group_id": 1020, "id": 807336}, {"user_id": 1, "stars": [], "topic_id": 21286, "date_created": 1303765600.113853, "message": "You don't have to think about whether it's going via REST, via websockets, or whatever...it's just \"messages\" that you can deal with in an evented way.", "group_id": 1020, "id": 807339}, {"user_id": 1, "stars": [], "topic_id": 21286, "date_created": 1303765626.32757, "message": "Then again, like you mention, now.js can be awesome too if you don't even want to think about it as messages, but instead as function calls.", "group_id": 1020, "id": 807342}, {"user_id": 15003, "stars": [], "topic_id": 21286, "date_created": 1303768549.89955, "message": "REST is not just a URL namespace philosophy. Building RESTful applications is a good practice when you are performing CRUD operations on \"resources\". If you are building a one-page app, it will help you come up with a consistent interface between your frontend and your backend.", "group_id": 1020, "id": 807726}, {"user_id": 22875, "stars": [], "topic_id": 21286, "date_created": 1303766125.831774, "message": "I was planning to use socket.io actually, but somehow got the impression that it didn't solve the issue of what format to use for passing messages back and forth.", "group_id": 1020, "id": 807406}, {"user_id": 1175, "stars": [], "topic_id": 21286, "date_created": 1303767570.9208691, "message": "socket.io is nice, but it's a very low-level layer. To do any kind of message dispatching you have to go to something else.", "group_id": 1020, "id": 807598}, {"user_id": 28604, "stars": [], "topic_id": 21286, "date_created": 1303766384.5721459, "message": "It depends on how your deployment of node.js is going to complement your existing service-based or domain-based platform. REST is a URL namespace philosophy and you may be suggesting implementation before making the hard decisions for your architecture. If you're not planning on building an API, you probably won't need to worry about exposing a URL structure.", "group_id": 1020, "id": 807443}, {"user_id": 22875, "stars": [], "topic_id": 21286, "date_created": 1303768527.261992, "message": "cool, thanks", "group_id": 1020, "id": 807722}, {"user_id": 1175, "stars": [], "topic_id": 21286, "date_created": 1303767588.6410811, "message": "What are you trying to do? as others point out, if you need a public API, REST might make sense.", "group_id": 1020, "id": 807599}, {"user_id": 1175, "stars": [], "topic_id": 21286, "date_created": 1303768471.9184389, "message": "Take a look at the socket.io docs. could be just what you need", "group_id": 1020, "id": 807716}, {"user_id": 22875, "stars": [], "topic_id": 21286, "date_created": 1303768789.4977629, "message": "@thmzlt That gets to the heart of why I asked this question. The reason I have doubts is that it imposes some overhead (assembling URLs on the client side, and parsing them on the server) without a lot of obvious benefit.", "group_id": 1020, "id": 807759}, {"user_id": 22875, "stars": [], "topic_id": 21286, "date_created": 1303768113.6430759, "message": "@mwhooker it'll be a small project with no public API, just want to use good practices in anything I do. Chat has been done to death... I was going to try a real-time auction system.", "group_id": 1020, "id": 807676}, {"user_id": 1175, "stars": [], "topic_id": 21286, "date_created": 1303769843.519315, "message": "though I do love the structure REST gives you. most RPC interfaces I've seen are a nightmare", "group_id": 1020, "id": 807879}, {"user_id": 1175, "stars": [], "topic_id": 21286, "date_created": 1303769765.122206, "message": "A lot of the overhead involved with REST (i.e. URIs) finds its strength in the semantic web. statelessness, self-description, and the decoupling of a resource from its representation", "group_id": 1020, "id": 807874}, {"user_id": 1175, "stars": [], "topic_id": 21286, "date_created": 1303769793.8388889, "message": "now sure how well that applies to a channel between a service and a single consumer", "group_id": 1020, "id": 807875}, {"user_id": 15003, "stars": [], "topic_id": 21286, "date_created": 1303770122.021549, "message": "@mwhooker doing all the work Pusher has already done for you :)", "group_id": 1020, "id": 807907}, {"user_id": 15003, "stars": [], "topic_id": 21286, "date_created": 1303769924.4286499, "message": "@akavlie I think that, no matter what, you'll need to assemble messages on the client side and parse them on the server side. Nevertheless, I agree with socket.io being an elegant solution (although not the easiest to implement).", "group_id": 1020, "id": 807887}, {"user_id": 15003, "stars": [{"date_created": 1303825271.633455, "user_id": 275}, {"date_created": 1306228228.691556, "user_id": 26065}, {"date_created": 1306649395.1937301, "user_id": 12535}], "topic_id": 21286, "date_created": 1303769963.5101891, "message": "You might consider http://pusher.com/.", "group_id": 1020, "id": 807891}, {"user_id": 1175, "stars": [], "topic_id": 21286, "date_created": 1303769967.5321679, "message": "@thmzlt mind talking about difficulties of implementing?", "group_id": 1020, "id": 807894}, {"user_id": 25851, "stars": [], "topic_id": 21286, "date_created": 1303828824.6814439, "message": "@akavlie toviefor.com uses Node.js and socket.io for real-time auctions, so it should be a good place to start.", "group_id": 1020, "id": 815098}, {"user_id": 15929, "stars": [], "topic_id": 21286, "date_created": 1303872712.230659, "message": "https://github.com/andyet/capsule", "group_id": 1020, "id": 821059}, {"user_id": 15929, "stars": [], "topic_id": 21286, "date_created": 1303872750.830713, "message": "Capsule is an experimental web framework by @HenrikJoreteg for Node.js that uses Socket.io and Backbone.js to synchronize model state by sharing model code between the client and the server.", "group_id": 1020, "id": 821061}, {"user_id": 15929, "stars": [], "topic_id": 21286, "date_created": 1303872801.0056851, "message": "aka still infant... however it looks very promising.", "group_id": 1020, "id": 821064}, {"user_id": 29659, "stars": [{"date_created": 1306228277.2808211, "user_id": 26065}], "topic_id": 21286, "date_created": 1303899476.5021949, "message": "I've used Faye http://faye.jcoglan.com/ for nodelytics (my experimental real time stats) and it works very well...", "group_id": 1020, "id": 824100}, {"user_id": 32812, "stars": [], "topic_id": 21286, "date_created": 1306222098.693723, "message": "+1 for Faye. I use it in a simple monitoring app at work and it works amazing.", "group_id": 1020, "id": 1162985}]