The current Tempus application is made following the client / server logic, where a client connects to the Tempus core through a HTTP+WPS protocol. This involves setting up an HTTP Server with a FastCGI configuration to a tempus core.
For simple use cases (test on a local machine with a single user), things may seem a bit complicated.
Simplify the client / server architecture so that it can "just work" on a local machine with a single user.
Possible solutions: embed a micro http server
mhugo
commented
7 years ago
The current Tempus application is made following the client / server logic, where a client connects to the Tempus core through a HTTP+WPS protocol. This involves setting up an HTTP Server with a FastCGI configuration to a tempus core. For simple use cases (test on a local machine with a single user), things may seem a bit complicated.
Simplify the client / server architecture so that it can "just work" on a local machine with a single user. Possible solutions: embed a micro http server