Thank you all for helping me to prepare my project proposal. Specially Jan, Robert and Alexander.
On 26 March 2015 at 06:57, Buddhika Jayawardhana <[email protected]> wrote: > Dear Jan, > I felt like it is better if I can include a design document(But I doubt > whether it can be done within today). Also more details about tools that I > am going to use.(IDE s, documentation tools, project management tools ect). > I am working in Ubuntu and not using any specific IDE ro documentation in > practice for Erlang. I am using vim and terminal. I searched a little bit > and found many people use emacs. I would like to know From your experience. > > > - Some good IDEs : for both Erlang and JavaScript > - A documentation tool > - A project management tool: if there any other than JIRA > - Any other tool which is worth to get familiar with for this project. > > Thank you so much for pointing resources to lean about stdio. "Advanced > Programming in the Unix Environment" book is available in our library. I'll > try to borrow it today or next Monday. > > Thank You. > > > On 26 March 2015 at 06:35, Buddhika Jayawardhana < > [email protected]> wrote: > >> This is my idea. >> >> *Benchmarking.* >> >> As Jan suggested lets use databases and typical functions to test the >> performance. We can use the same tests with old query server and we can use >> that date for comparing.I will add these thing to the proposal >> >> *Moving to Node/io.js* >> >> I am not experienced enough to make a decision. I should be able to >> complete what ever included in to the proposal within the summer. I think >> it is better if experienced members of the community can come to a >> decision. >> I am planning to upload the final proposal around 2.00 UTC tomorrow. It >> would be really easy if we can come to a decision before that time. >> >> On 26 March 2015 at 02:30, Alexander Shorin <[email protected]> wrote: >> >>> On Wed, Mar 25, 2015 at 11:34 PM, Jan Lehnardt <[email protected]> wrote: >>> > They are separate goals, but it would be exceptionally hard to build >>> > a streaming protocol in couchjs. It very likely would require >>> significant >>> > work in C/C++ (unless I’m missing something obvious). That’s why I >>> > think a new protocol and a new JS interpreter is going hand-in-hand. >>> >>> In transport remains stdio, there is nothing need to do now. Since 1.3 >>> release couchjs technically supports streaming (you can try to call >>> getRow() from view function to prove that), but protocol itself is >>> not. If you're going to provide socket-driven transport then yes, some >>> C++ hackery might be required. >>> >>> -- >>> ,,,^..^,,, >>> >> >> >> >> -- >> *Buddhika Jayawardhana* >> Undergraduate | Department of Computer Science & Engineering >> University of Moratuwa >> *[email protected] <[email protected]>* | LinkedIn >> <http://lk.linkedin.com/in/buddhikajay/> >> > > > > -- > *Buddhika Jayawardhana* > Undergraduate | Department of Computer Science & Engineering > University of Moratuwa > *[email protected] <[email protected]>* | LinkedIn > <http://lk.linkedin.com/in/buddhikajay/> > -- *Buddhika Jayawardhana* Undergraduate | Department of Computer Science & Engineering University of Moratuwa *[email protected] <[email protected]>* | LinkedIn <http://lk.linkedin.com/in/buddhikajay/>
