#526 Investigate using Tomcat for TPS subsystem
Closed: Fixed None Opened 9 years ago by nkinder.

We should investigate moving TPS from httpd to Tomcat. We want to do some cleanup and refactoring of the TPS code anyway, and it might just make more sense to port it to Java and use Tomcat like most of the other Dogtag subsystems.

Things we specifically need to look at are:

  • Does Tomcat provide support for chunked-encoding?
  • Are we able to share existing shared Java code with the other subsystems
    (allowing us to get rid of things we have duplicated in C just for TPS)?
  • Compare the effort of cleaning up our existing C code vs. rewriting in Java.

As a part of this investigation, we should look at all other functionality we are looking at adding to TPS and take that into account when deciding the approach to take. If we would have to rewrite large portions of TPS to implement new features, it might just be better to move to Java/Tomcat at the same time.


We have an initial framework that uses Tomcat for TPS. Specific details will be dealt with in new tickets.

master:

  • 0812c8d7583250d9ccbfbc3439083d1d2296b2f5
  • 99e5dc7fec0cc9c4b78ab694e55e6c484e497d2f

Metadata Update from @nkinder:
- Issue assigned to edewata
- Issue set to the milestone: 10.1 - 06/13 (June)

5 years ago

Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new
issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.

This issue has been cloned to GitHub and is available here:
https://github.com/dogtagpki/pki/issues/1096

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.

Login to comment on this ticket.

Metadata