@Paracoder wrote:
Hello all!
I’ve been pouring over frameworks for the past week - research, test, run into a problem, find out it requires a billion dependencies and/or don’t fit the build structure we are needing…
As such, I’m hoping that I can get some clarification regarding the capabilities of this framework in this setting…
We have 3 parts to our environment:
- UI hosted (anywhere - not embedded)
- Node.JS Server as controller
- Java Server as the backend computational/database access point
We have our reasons for requiring the separation between UI and the Java Server and or UI and the database… please do not reply with “well you should just drop the Java” or “drop the Node.JS”… this is being built in the context of financial institutions and therefore requires a greater level of processing and separation.
What I did:
Created a ‘vanilla’ JS/jQuery UI which can request dialogs/data from Node.JS - which authenticates the user, requests the data, and then generates “on the fly” a new (div) window for the user.
The problem with this is rather obvious: while it works for now, any changes in either code can complicate things - and we’ll be hiring developers who need to “pick it up and run with it” once the infrastructure is complete.
As such, I’m looking for a way to do this:
User Requests Info -> UI -> send request over WebSockets -> Node.JS takes request, authenticates, and replies with a dataset and name of the dialog to make -> UI generates dialog with attached data, and passes it on to the user once completed.
As this is meant to be a SPA, and we’re avoiding routing as the idea is to load a new div in the same ‘index.html’, I had looked into Vue.js but ran into serious issues with the WebSocket implementations as the compiling required complicates data retrieval over WebSockets, and Socket.IO … while functional, is not enough of a ‘standard’ to be used in this way. The Java server is also using (pure) WebSockets, so we don’t want to have to do some “loop” when they could all “speak the same language”.
Ideally, we do not want Node.js compiling or spitting out any html or views within it - as in the future a mobile app or other entry point may be added, we need generic ‘envelopes’ to be sent across the wire, allowing the UI to handle their output.
I.e. :
envelope = [ header: “infoRequest”, body: { // array of info } ]
Based on the header, it will then pass off the body to the appropriate function for loading.
If this can be done within Ember.js using websockets as communication, without routes and Node to do the generation… please point me in the right direction!!
Thank you for your time, look forward to the feedback.
Posts: 1
Participants: 1