Olga suggested I run with Flask or Cherrypy. Both seemed quite similar and fulfilled the same purpose- providing the API for a web server.
Choosing the Flask API, I started implementing several server-side operations at a functional level. I used the server's file system to do storage.
- PUBLISHER_REGISTER and SUBSCRIBER REGISTER
- A POST that registers the publisher/subscriber by storing their public key.
- A GET operation that tells a publisher/subscriber information about a target entity.
- A POST that allows publishers to add subscribers.
- A POST that lets subscribers request to join a group
- Publishers GET membership requests from the previous JOIN_GROUP for a particular group
- Deletes a subscriber from all of its groups, freeing up space in the server
- Publisher POST that removes a member from a group
- New encrypted group keys must be uploaded eventually via UPDATE_GROUP_KEY
- Subscriber GET request that retrieves his/her encrypted group key for a particular group
- Publisher GET command that retrieves the members of a group he/she created
- Follow-up to DELETE_MEMBER
- Publisher POST that uploads new encrypted group keys to everyone who wasn't deleted
- A GET request by publishers to get a unique Group ID for the keyserver.
- Also registers that group for the publisher
- GET request by subscribers that shows what groups he/she is a part of
- GET request by subscribers that shows what groups a certain publisher is in charge of
All of these are done on some level aside from UPDATE_GROUP_KEY: That function probably needs some thought first. Perhaps we should use a special file structure that contains users and encrypted keys, which could be parsed by the file server
Additionally, verification will have to be implemented: We don't want the key server to allow a non-creator publisher to delete members of a group :)