Support for other Web Servers

[timur-han]

Hi,

Are you planning to support any other web servers in the near future?

The library looks quite promising but usage with only Aleph limits its adoption. (I have nothing against Aleph but probably its not the most commonly used one)

Regards,

Timur

[ztellman]

Hi Timur,

Aleph is a Ring-compliant server, and is designed to be a drop-in replacement for any application relies on that functionality. Are there obstacles to switching that I'm unaware of? I'd like to provide documentation for any common issues encountered during swapping out servers.

Zach

[malcolmsparks]

Hi Timur,

I am planning to support other web servers in the near future. Right now, yada is closely tied to Zach's Aleph and Manifold libraries and in some cases relies on being able to return Manifold deferreds and streams directly to the web-server, with back-pressure support. In other cases such as multipart/* and application/octet-stream request bodies which yada processes asynchronously, it relies on being able to get the raw-stream from Netty, which Aleph provides.

It's not that other modern Java web-servers don't have this functionality, more that there is not a consistent API to these facilities so I will have to work out how to support each in turn.

[timur-han]

HI all,

@ztellman no it's not about Aleph, Aleph is quite a nice drop-in replacement.

The thing is that only it would be nice if Yada could provide us the flexibility to move from one ring complaint web server to another.

@malcolmsparks thanks for the answer!

Timur