Stuff

REALLY got off from what I was planning on doing today. The split is complete, the web doesn’t use ANY DB stuff anymore (Wahoo!). Instead, there’s a new internal service that just the web uses, that can be used signup and validate a new user. It was kinda a pain, but it looks like it all works ok.

One other thing I’ve been aware I needed was some kind of logging. This is mostly to be able to track what’s going on, but also to be able to eventually be able to “roll back” actions. I’ve created a new logging class that can log to the DB (well, it logs to the DB ATM, in the future that could be a file, event log, whatever). Anyway, it shows the type of msg (location, login, logoff, etc.) and if it’s a log action, the type (add, delete, view, update, etc.). I’ve just added it into the “happy” paths, but it works pretty good. I will need to scale this up and down. If I’m not having a lot of trouble on and have more users, don’t really need to see every “CanAccess” and “view” action that happens.

Oh, and this is all inside of the Location Service, so both the web and external systems will be hitting it.