Building The Server Pipeline
With work progressing well on the MOOVPAD webAPIs in general, it's time to shift the focus on to the MServer pipeline that will connect these and the MOOVPAD apps, as well as the primary service databases. This shift is important right now because it will help fill in some of the blanks, with the results carried over to subsequent APIs without repeating the work.
The goal is to just get the main structure of this pipeline, handling the events and any specialised system function calls, to the point where all the generic elements are accounted for. Then any specifics related to particular APIs can be added later. I have the main objects of this pipeline already mapped out roughly. So just adding more detail in the code. What I can say for now is that once completed, the functions will provide some powerful service tools for later use.
Work continues, and I hope you guys are having a great day 🙂
Stay awesome,
EMh
HOW MOOVPAD IS BEING BUILT
For the overview of how MOOVPAD apps are being developed, the reasoning behind particular decisions during development, policies, and more in relation to all the technical things, please see the link to the left.
This will be an ongoing work in progress, and will always be linked to the bottom of each upcoming Blog post.