oci-pronghorn/greenlightning

High performance microservice runtime

greenlightning's Issues

No readme?

Support for more encoding types beyond utf8

Content type can have lesser used encodings which must be applied.

Better support for large payloads

Hi,

I'm working on moving a REST API from Tomcat to GreenLightning. On average, the API takes in a list of 100 items to update, but occasionally can receive requests with 1000 or even 10000 items. Because of this, I have to set the max request size to 600000 and the heap size to 12GB. Even when I do this, I have to set the concurrency parameters very low or I run out of heap. Also with such a large heap, garbage collection times are unacceptably long. Are there any ways to get around this, or perhaps any future plans for streaming chunks of the request through to be processed separately?

Thanks,
Jason

Large chunked post support from client side call.

Http clients can post but large chunked posts should be declaritive and easy.

Central Repository, Bintray...

Are you planning to deploy the library on any maven repository?

Optional --s argument

Hi,

I want to use this java http server as a custom "default-http-backend" for a kubernetes ingress, but it is not possible to satisfy this requirement:

• Serve a 404 page at /

GreenLightning is started with a required argument that specifies the default landing page, so it ends there.

In addition, it will be nice if GreenLightning do a redirect to 404.html, 500.html, 403.html, etc.. static pages according to the http error code at response.

Declarative form post parse

Like the json support add form field extract support.