Hi Chris, A few comments/questions:
- what happens when the server is flooded with requests? I would think that DeltaQL's broadcast would result in too much chattiness, unless it timed the response. For example, I see how DeltaQL would be a great fit for a Dashboard, but if I'm hitting a table *very* often, it probably wouldn't make too much sense to broadcast every single change. If I could specify a timer, say 3 seconds, that would still be useful and would use less bandwidth. I would like to optimize bandwidth even if this means to sacrifice real-time data. - the jargon could be made a little more self-explanatory (what's the difference between Head and Tail? It has the same description.) - what are the operations you can perform via Lop? - how is ResultList kept ordered? By applying a Sort operation? If not present, what happens? (unordered? fails?) - it would be great to see a small examples below each Jargon item. Very cool idea Chris, but I'd like to see better documentation. With better docs people will be able to make better recommendations, I suppose. Cheers, -- Tito On Apr 5, 2012, at 5:51 AM, Chris Dew wrote: > Hello everyone, > > I'm trying to get a little feedback on the API and goals of DeltaQL. > > DeltaQL is a NodeJS library which gives you all the tools you need to create > datastores whose query results never get stale. You create your queries with > a LINQ-ish series of functions - changes to the data on which the query is > based automatically update the pages in browsers. > > Previously I've built a couple of NodeJS/SocketIO/KnockoutJS systems for > soft-realtime browser-based reporting. They have typically connected to some > external data streams, maintained some local state, persisted state to disk > as JSON, or via MySQL and produced in-browser tables, graphs and gauges which > update in soft-realtime (typically < 100ms) as new data comes in from these > external streams. > > I analysed what they had in common, and decided to build a framework to make > the creation of similar app easier for me (and others) in the future. > > I'd love for people here to have a look at > https://github.com/chrisdew/deltaql#readme and give me some feedback on: > > a) will this be of use to other people and > b) do you have ideas or improvements, especially to the API. > > This project is still at a very early stage - nothing is officially > 'released' and much is broken or not yet implemented. I have implemented > enough to get the DeltaQL Bootstrap project working, though it would probably > take an hour of your time to make it go (as I haven't published the NPM > packages, or even audited the dependencies recently). > > If you're interested seeing how this project pans out, email me at cmsdew AT > gmail.com, follow @chrisdew on Twitter or watch the project on GitHub. > > Thanks, > > Chris. > > -- > Job Board: http://jobs.nodejs.org/ > Posting guidelines: > https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines > You received this message because you are subscribed to the Google > Groups "nodejs" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/nodejs?hl=en?hl=en -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
