Hey,
> 1.node.js is event driven, so best suited for real time chat (or video > streaming etc.). > Meteor was recently integrated with React and other wonderful frontend javascript frameworks. Since the project is more about rendering and front-end capabilities, react will help us in doing front-end operations faster! > > 2. "It is not advisable to use Node.js for CPU intensive applications" > Site : http://www.tutorialspoint.com/nodejs/nodejs_introduction.htm > We use OGV just as an online viewer. The way it works is, the user uploads a file, there is some backend processing using the brlcad software. All you'll need OGV is for uploading and viewing (at user's end). The CPU will be required only for running the commands (like gToObj) which will also be the case while using PHP MVC. > Node.js is a different beast and server-side apps run permanently. You’ll > need a real/virtual/cloud or specialist server environment, ideally with > root SSH access. That’s a step too far for some hosts, especially on shared > hosting where you could bring down the whole system. > Node.js hosting will become simpler, but I doubt it’ll ever match the ease > of FTP’ing a few PHP files. > Site : http://www.sitepoint.com/sitepoint-smackdown-php-vs-node-js/ > I don't thinks that this will be a major issue in our use case. > I do not envisage OGV to need event / I-O driven features like Real time > chat, streaming video etc. But it will have CPU-bound workload like .g to > .obj file conversion, many other tools etc. > Like I said, this will be the case for any backend framework we choose. We'll anyways have to use g to Obj conversion whose performance will depend on CPU load rather than backend tech. > So I recommend PHP - CI implementation (But I am open to Node.js > implementation too as much of the work is done) > Going through both the project my study is PHP implementation has more and > clear documentation > <https://github.com/BRL-CAD/geometry_viewer/tree/master/doc>. > > Node.js lacks the proper documentation > I don't think so! Its javascript. You can do anything with it. So as far as the proposal and patch is considered- 1. If you concentrate on PHP-CI This will require some extensive work on your proposal and patch. Your proposal should concentrate majorly on almost everything, every single functionality, database structure, workflow, UI, used libraries, deployment etc. The patch you submit won't be exactly a patch but a new repo altogether which should convince the mentoring organization that the project can be done and deployed in the given time. I would suggest you to make a working demo of file upload, g->obj conversion and then basic model viewing in the browser. Also include UI and workflow ready. 2. If you choose to use Meteor You proposal should primarily concentrate on deployment. Deploying Meteor app on Free-BSD server. Your patch should tell us that you are familiar with Meteor and mongoDB. You can make a branch from 'maser', and work on something like viewing the model using different views like wireframe, adding color, transparency etc. Authentication is too easy to implement in Meteor, would suggest not to do that. -- Regards Shubham Chauhan
------------------------------------------------------------------------------
_______________________________________________ BRL-CAD Developer mailing list brlcad-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/brlcad-devel
