Separate HTTP server implementation from Tigase HTTP API (#4)
Closed
Andrzej Wójcik (Tigase) opened 1 decade ago

Currently we are using Jetty as an HTTP server and in current code of Tigase HTTP API we are using Jetty API directly to access Jetty and start/stop HTTP server or to add/remove modules. It would be good idea to remove any Jetty specific code from Tigase HTTP API and move it to new project called something like Tigase HTTP Server provider - Jetty. This new project would allow us to keep Tigase HTTP API clean of direct dependency on Jetty and also will make a possibility to implement and use other server provider in future.

Andrzej Wójcik (Tigase) commented 1 decade ago

Removed Jetty dependencies from main classes and moved Jetty dependent classes to separate package.

Andrzej Wójcik (Tigase) commented 1 decade ago

Added support for HTTP server embedded in some JDK implementations.

Andrzej Wójcik (Tigase) commented 1 decade ago

Moved Jetty dependent classes to separate project Tigase HTTP API - Jetty HTTP Server and updated Jetty to 9.2.1, so now it will use latest current stable version of Jetty.

issue 1 of 1
Type
Task
Priority
Normal
Assignee
RedmineID
1917
Issue Votes (0)
Watchers (0)
Reference
tigase/_server/tigase-http-api#4
Please wait...
Page is in error, reload to recover