Thad Humphries wrote:I have a requirement for a web client to work with a large, legacy server system. This system has an API of approximately 200 functions and is documented in C. The system also provides C libraries for Windows and Macintosh development, and we have rolled our own Java interface.
When I've investigated the RPC claims of languages outside of C, what I find are examples of an application talking to another app in the same language and no mention of legacy systems. As I said, for Java we had to roll our own--writing our own RPC hand-shaking and packing and unpacking parameters for each call. This was no small effort. What might Node.js offer that would get me moving quickly?
Kent O. Johnson wrote:Hello Mike, Mark, T.J., and Nathan! Welcome to the ranch.
My question to you is how do you address security with node.js? After looking at your ToC for the book I see you address security with HTTPS in chapter 4 and Connect in chapter 7.
I see that the Node Firm claims to provide node.js with enterprise-level security. Do you address that topic or point in your book anywhere?
Muhammad Saifuddin wrote:Hi Authors,
Firstly, Congratulations and best wishes for this book.
My Question is more to share-out your part of interest like How you become enthusiast of this product and what attract you most in your first experience?
David Sachdev wrote:
Barry Raczkowski wrote:Okay now I understand where Node.js fits in to the chain. Can it connect to database back end were does it sit in the server software chain. Does it work with python or is it self conatined? Does it have JDBC drivers? Can it perform ajax calls?
When it comes to it's connection pooling and transaction capabilities, can Node.js handle XA transactions across multiple databases? Can it rollback transactions against various "data sources"
Sagar Rohankar wrote:I am asking this question because I really want to know what he is doing after stepping down as node lead? Any idea authors?
Priyadarsan Khabiya wrote:Which unit testing framework is being used in node.js in action and why ?
Chip Furstenau wrote:This is a similar question to one that was already posted, but here goes. Whenever I read articles about Node.js, it seems to have a reputation as a "neat trick" for web developers to easily create a little backend for their application. Are there benefits to Node.js that could motivate someone who is already familiar with Java backend to learn a new framework? That is, could an existing application be made better by implementing Node.js?
Scott J Johnson wrote:Hi!
So I've noticed that a number of projects use grunt to 'build' a node.js project. I'm wondering what projects that use node.js need to do to "build", and what advantages/disadvantages are of different tool sets.
Alec Swan wrote:Hello,
What are the pros and cons of node.js when compared to a Java backend, such as Jetty? I am looking for something very high-level, e.g. "Use Java for data-intensive processing" or "Learning curve of asynchronous programming for Java developers is very steep". It would be valuable if the answer touched on performance, productivity, adoption and tooling of these two backend technologies.
Qunfeng Wang wrote:Developing with a dynamic language is a little painful. It happens a small typo will cause some time to debug. I'm wondering how comfortable developing server side with Node. It's different with client side. We have no choice on client side. But there are lots of good languages for the server side.
robyne vaughn wrote:Hello,
I tried to look at the sample chapters, but the links push you to an opening page, and on a quick glance, I didn't see any sample chapters to download.
I am new to mobile and web app development. I'm still trying to determine the best tools to use and best practices. There are so many options. For the moment, my team has started with Eclipse. We're using some jquery mobile and trying to figure out phone gap. We have developed a couple of Android apps which use a restful web service and pull json data from our DB2/LUW database. We expect to build an Apache Tomcat web server after we reach a certain point. For now, we're serving from Eclipse/tomcat.
In our googling around about how to do what, we cross trails that point to Node.js, but since we have started down a path, we hate to add still one more thing to learn, especially since we're still in the "feeling our way through" stage.
Can you tell me what is Node.Js's primary purpose, what need it fills and why we should consider using it?
Then, is your book good for the novice?
Federico Kereki wrote:Hi! What's the current (better?) way of hot patching some JS code in use at a node.js server? With Apache, I can just change a PHP file, and from then on, it will be used, but with node.js, it doesn't work that way. I've read about several possible methods, but no one seemed to be as simple as Apache's. What would you recommend?