Fwd: HTTP/3 in Eiffel - are you interested?
32 views
Skip to first unread message
Alexander Kogtenkov
Dec 12, 2018, 12:40:42 PM12/12/18
to eiffel-web...@googlegroups.com
Dear developers,
This is a duplicate of the message sent to the Eiffel users mailing list to see if there is any interest in the project among subscribers of this group.
Best regards,
Alexander Kogtenkov
This is a duplicate of the message sent to the Eiffel users mailing list to see if there is any interest in the project among subscribers of this group.
Best regards,
Alexander Kogtenkov
Dear Eiffel developers,
One of the libraries actively used in several projects across the world is EiffelWeb. Started as EWF (Eiffel Web Framework) a few years ago, it is still under active improvements coming from both the original authors and the developers who use it. Among other facilities, it provides connectors that allow for using an Eiffel application in different environments, supporting CGI or FastCGI, or even to run the application as a standalone web server.
Internally, these connectors rely on HTTP/1.1, a stable and rather old standard. With the new requirements and understanding of network usage, more secure and efficient protocols emerge. HTTP/2 was released 3 years ago. And this November, a working draft for HTTP/3 (https://en.wikipedia.org/wiki/HTTP/3) was announced. The latter is built on top of TLS 1.3 right from the beginning, so the security does not introduce an additional layer of overhead. And, the protocol is based on UDP to allow for better performance of applications where response time is important - such as media streaming. All together this introduces quite interesting and non-trivial challenges for implementers. Some major players, including web servers, wide-spread browsers, and even the well-known cURL project have joined the effort to implement the protocol.
What does it mean for Eiffel community? As soon as cURL library is updated to support HTTP/3, the corresponding Eiffel binding can be updated to support the new functionality and new API. This is expected to be more technical rather than new development work. But for the server side, more efforts are required. Some changes might be required to support the protocol for CGI and FastCGI connectors. And a completely new implementation is required to support a standalone connector that allows to expose an Eiffel application as a web server. Is it something you or your company need in a couple of years? Is your projects going to be used together with modern software with performance and security requirements? Do you want to work on the development of HTTP/3 implementation in Eiffel, and, if yes, how much time you can devote to it?
Supporting a new network protocol is not an easy decision: it requires quite a bit of resources and cannot be finished in a couple of months. We are looking for your feedback on the questions, from both sides - those who needs the functionality and those who can participate in the work. This will direct future evolution of EiffelWeb: shall we dive into this new technology, shall we let web servers to do all the necessary work and keep HTTP/1.1 for standalone Eiffel applications, or shall we focus on application-side functionality without adding support for any new HTTP releases.
Thank you for comments and best regards,
Alexander Kogtenkov for the Eiffel Web community project
One of the libraries actively used in several projects across the world is EiffelWeb. Started as EWF (Eiffel Web Framework) a few years ago, it is still under active improvements coming from both the original authors and the developers who use it. Among other facilities, it provides connectors that allow for using an Eiffel application in different environments, supporting CGI or FastCGI, or even to run the application as a standalone web server.
Internally, these connectors rely on HTTP/1.1, a stable and rather old standard. With the new requirements and understanding of network usage, more secure and efficient protocols emerge. HTTP/2 was released 3 years ago. And this November, a working draft for HTTP/3 (https://en.wikipedia.org/wiki/HTTP/3) was announced. The latter is built on top of TLS 1.3 right from the beginning, so the security does not introduce an additional layer of overhead. And, the protocol is based on UDP to allow for better performance of applications where response time is important - such as media streaming. All together this introduces quite interesting and non-trivial challenges for implementers. Some major players, including web servers, wide-spread browsers, and even the well-known cURL project have joined the effort to implement the protocol.
What does it mean for Eiffel community? As soon as cURL library is updated to support HTTP/3, the corresponding Eiffel binding can be updated to support the new functionality and new API. This is expected to be more technical rather than new development work. But for the server side, more efforts are required. Some changes might be required to support the protocol for CGI and FastCGI connectors. And a completely new implementation is required to support a standalone connector that allows to expose an Eiffel application as a web server. Is it something you or your company need in a couple of years? Is your projects going to be used together with modern software with performance and security requirements? Do you want to work on the development of HTTP/3 implementation in Eiffel, and, if yes, how much time you can devote to it?
Supporting a new network protocol is not an easy decision: it requires quite a bit of resources and cannot be finished in a couple of months. We are looking for your feedback on the questions, from both sides - those who needs the functionality and those who can participate in the work. This will direct future evolution of EiffelWeb: shall we dive into this new technology, shall we let web servers to do all the necessary work and keep HTTP/1.1 for standalone Eiffel applications, or shall we focus on application-side functionality without adding support for any new HTTP releases.
Thank you for comments and best regards,
Alexander Kogtenkov for the Eiffel Web community project
lar...@moonshotsoftware.com
Aug 12, 2021, 9:18:37 PM8/12/21
to Eiffel Web Framework
Did you ever get any feedback on this?
You mention UDP. I went to Kiwi Syslog and they no longer have a "FREE" option, just a purchase and 14-day trial. So, it made me wonder if I could build an Eiffel standalone server to consume UDP to build a Syslog server?
Alexander Kogtenkov
Aug 25, 2021, 9:13:27 AM8/25/21
to eiffel-web...@googlegroups.com
No, there were no replies.
Alexander Kogtenkov
lar...@moonshotsoftware.com <lar...@moonshotsoftware.com>:
--
--
You received this message because you are subscribed to the Google
Groups "Eiffel Web Framework" group.
To post to this group, send email to
eiffel-web...@googlegroups.com
To unsubscribe from this group, send email to
eiffel-web-frame...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/eiffel-web-framework
See the site for the Eiffel-Web-Framework project at
https://github.com/EiffelWebFramework/EWF
---
You received this message because you are subscribed to the Google Groups "Eiffel Web Framework" group.
To unsubscribe from this group and stop receiving emails from it, send an email to eiffel-web-frame...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/eiffel-web-framework/fabe80e9-c9b9-48cf-b263-5c299173729bn%40googlegroups.com.
Anders Persson
Aug 29, 2021, 7:20:17 AM8/29/21
to Eiffel Web Framework google groups
Hi
I am using the HTTP/1.1 for standalone Eiffel applications. I am interested in support for a standalone server also in the future. How would it impact that solution if EWF is not updated to HTTP/3?
I am able to spend some time to verify the HTTP/3 solution by comparing it to my current HTTP/1.1 implementation.
To view this discussion on the web visit https://groups.google.com/d/msgid/eiffel-web-framework/1629897203.474881992%40f401.i.mail.ru.
Reply all
Reply to author
Forward
0 new messages