If you're feeling like refactoring a bunch...
We should probably just instantiate the servlets in sydent/httpserver.py instead of in sydent/sydent.py.
I see no reason for them to be stored on the sydent object.
I concur. Writing this down as a task for the future. Eyeballing it, I'd suggest:
move Servlets class into httpserver.py
store servlets attribute on ClientApiHttpServer instead of Sydent
looks like we'll need to pull out the replicationPush servelet because that's only used on ReplicationHttpsServer
Tests will need updating because they refer to servlets.
Personally, I think the various http servers should NOT keep a reference to the Sydent object around; the Sydent object should pass what's needed to them at construction time (or maybe setup() time).
@clokep writes:
I concur. Writing this down as a task for the future. Eyeballing it, I'd suggest:
servlets
attribute on ClientApiHttpServer instead of SydentPersonally, I think the various http servers should NOT keep a reference to the Sydent object around; the Sydent object should pass what's needed to them at construction time (or maybe
setup()
time).