node-restful | quickly providing a REST API | REST library

Think of Express as an incredibly lightweight and basic framework that's very closely wrapped around the core of NodeJS. Most of the problems you're having aren't Express specific, they're just different npm packages that extend or alter the core functionality.

1. The way that the data is parsed by the application matters. Academind can handle image uploads because it uses the multer package. This is a middleware that handles any requests done with the multipart/form-data encoding type, which is how images are sent to the server. Expected encoding types are also the answer to #5.

2. The two files are just personal preference. You can do everything in one file, but many people like to require the app.js in their server.js to further separate the "duties" of each file.

3. This is similar to above, how they're separating the duties of the files even further. If you look closely, both are eventually ending up being called with the router. By creating Controller files in one of the projects they're separating whats called the "business logic" from the route definitions. It does the same thing, but some consider it more organized.

4. Are the two parameters vs three parameters req, res, next? If so, those are actually available for every single route in express. A lot of the time you don't need next in your code so programmers will just leave it out.

5. This comes back to the expected encoding type of your request. Various middleware will handle and allow different encoding-types as needed. https://github.com/expressjs/body-parser is probably the most popular one as it's built into expressjs. This is how it interprets the requests you make and sets the req.body object. The "params" type actually sets the values as part of the url, appending them like so: 127.0.0.1:3000?param1=test&param2=test. Where form-data is a part of the request that's being made and isn't available as a get parameter.

I hope this helps make more sense for you!

Edit: Based on your comment below, NodeJS functions using a lot of different middleware. Theoretically you could do this any number of times if you want to, and just keep using next to go to the next function in the middleware.

Ex:

Kind of dug into it and made an extension to change driver reference

Here are all the changes, hope it helps someone in future :)

extensions/restful/index.js

you would have to do the following in your route:

I figured it out! I was not getting the values in the array that was being posted.

removing this part:

You are using a mongoose model object to do

I'm not very familiar with the exact technologies you are using, but from a structure/ logic flow standpoint maybe this will help:

I think your issue might be that you parse the entire file into memory before processing: that's a lot to hold on to when in reality you just want to process one word at a time. Some quick Googling lead me to this article which makes it seem like you could read a line from your file, count it, insert your shape and then move on to the next word which should prevent you eating a ton of memory.

You can simply write a middleware for this kind of purpose. Clients will generally send tokens in header, so that you can get the header information and verify it. Your middleware will be something like this.