dservgun / erp Goto Github PK

Currently the TestRunner uses a wait (that can change to retry, though the core issue remains for testing):
TestRunner should be able to start the client connection thread only after the server has started.

Though not ideal, the mvar is set just before the call to
putMVar m "Started..presumably" WS.runServer "127.0.0.1" portNumber $ handleConnection m acid
This seems to work for now.

Based on the #haskell channel chat, using acid state for database persistence is not ideal and we need to copy state to persistent data store. Successful copy should remove the records from the acid state.

snap websocket
snap acidstate
for deployment. The current architecture is for testing purposes.

per @S11001001 and i guess general haskell guidelines, we need to avoid exceptions instances because they can get eaten up etc.
This issue is a catch-all to remove exceptions from the model.

webserver and acid should not be hosted on the same server.

Handle exceptions across the server: send the exception message back as a json response.
Design a response type in the server.

Cant test the application on mac.