Home/ Questions/Q 7031591
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-28T00:49:25+00:00

I’m planning on writing a spine/backbone.js style web application which basically just transfers a

  • 0

I’m planning on writing a spine/backbone.js style web application which basically just transfers a large application.js file to the client’s browser that communicates with the node.js backend using ajax. The problem is that I don’t know how to structure such a project, since I’ve never seen examples of such an application. I can picture some pros and cons with different ways of doing this

  • Keep everything in one project folder. Both the server side and client side code resides in the same folders which means they can share resources such as form input validation and language files. This seems like a good solution, but I have no clue how I would bundle only the code that the client needs, and not the server code. Just in general I don’t know how to accomplish this. If it has been done before, I would like to see some sample code, perhaps even a git repo

  • Create two separate projects. One for the client and one for the server. This seems a lot more simple and straight forward, but not as elegant when it comes to sharing resources. I would have to write code such as form input validation twice.

Any thoughts?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Your first situation is a very tricky scenario and I would suggest that we’re not quite there yet. Some would argue that there’s little reason to try to get there, as front/back ends will always be tasked with slightly and sometimes drastically different tasks. Libraries like derby show promise, but aren’t quite there yet.

    I discussed this recently with a friend and we came to the conclusion that perhaps the best bet for now would be to serialize models over websockets, and then ensure that the node server and client app stay in sync.

    I may work on such a library, but for now I’m still developing with 2 folders and copies of models on both sides. Layout mark-up gets sent from the server, with all other content rendered client-side after receiving JSON from the server. Frankly, the amount of duplication isn’t really that substantial. A little irritating but also maintains greater flexibility to grow in different directions.

    • 0