On Monday, February 11, 2013, Alexander Shorin wrote: > Ah, so how it works. Brilliant! > > But am I right, that os_process_limit should be raised for it (long > debug - long respond time) and there would be hard to locate > bottlenecks with such technique? Probably, next evolution step should > have profiler and frames stack tracer features with some backlog for > post-analysis. > > right :) we definitely need an improved protocol to handle thzt and more concurrency. also maybe using websockets in most parts.
benoît > -- > ,,,^..^,,, > > > On Mon, Feb 11, 2013 at 6:37 PM, Jason Smith > <[email protected]<javascript:;>> > wrote: > > All I am doing is using node-inspector, a web-based debugger. Any > language > > with a web-based debugger could work. CouchDB just proxies requests to > the > > debugger. > > > > So any language is possible. It's just that it was so easy with Node.js. > > > > > > > > On Mon, Feb 11, 2013 at 2:22 PM, Alexander Shorin > > <[email protected]<javascript:;>> > wrote: > > > >> Hi Jason! > >> > >> Any possibility to have such feature for other query servers? > >> -- > >> ,,,^..^,,, > >> > >> > >> On Mon, Feb 11, 2013 at 6:04 PM, Jason Smith > >> <[email protected]<javascript:;>> > wrote: > >> > I just pushed more work in my nodejs_couchdb branch. > >> > > >> > I have a working in-browser GUI debugger. You can set breakpoints, > step > >> > through code, inspect data values. This works for any JavaScript code > >> > CouchDB runs: map/reduce functions, validate_doc_update, filters, etc. > >> > > >> > I put up some quick screenshots and mp4 screencast to show what it's > >> like: > >> > > >> > https://jhs.iriscouch.com/files/debugger/debug.html > >> > > >> > I would love to hear feedback from people. What are your thoughts? > >> > > >> > Me? I think it shows the power of Node.js. It shows possible > opportunity > >> > cost if we do not use it. > >> > > >> > Thanks! > >> > > >> > -- > >> > Iris Couch > >> > > > > > > > > -- > > Iris Couch > > -- > ,,,^..^,,, > > > On Mon, Feb 11, 2013 at 6:37 PM, Jason Smith > <[email protected]<javascript:;>> > wrote: > > All I am doing is using node-inspector, a web-based debugger. Any > language > > with a web-based debugger could work. CouchDB just proxies requests to > the > > debugger. > > > > So any language is possible. It's just that it was so easy with Node.js. > > > > > > > > On Mon, Feb 11, 2013 at 2:22 PM, Alexander Shorin > > <[email protected]<javascript:;>> > wrote: > > > >> Hi Jason! > >> > >> Any possibility to have such feature for other query servers? > >> -- > >> ,,,^..^,,, > >> > >> > >> On Mon, Feb 11, 2013 at 6:04 PM, Jason Smith > >> <[email protected]<javascript:;>> > wrote: > >> > I just pushed more work in my nodejs_couchdb branch. > >> > > >> > I have a working in-browser GUI debugger. You can set breakpoints, > step > >> > through code, inspect data values. This works for any JavaScript code > >> > CouchDB runs: map/reduce functions, validate_doc_update, filters, etc. > >> > > >> > I put up some quick screenshots and mp4 screencast to show what it's > >> like: > >> > > >> > https://jhs.iriscouch.com/files/debugger/debug.html > >> > > >> > I would love to hear feedback from people. What are your thoughts? > >> > > >> > Me? I think it shows the power of Node.js. It shows possible > opportunity > >> > cost if we do not use it. > >> > > >> > Thanks! > >> > > >> > -- > >> > Iris Couch > >> > > > > > > > > -- > > Iris Couch >
