Re: [boost] [GSoC 2014] Http Server Proposal
Hi Vinícius, Perhaps it's not bad to look at what Artyom Beilis does with cppcms : [http://cppcms.com/wikipp/en/page/main ](http://cppcms.com/wikipp/en/page/main)And others things like [https://github.com/metagoto/fcgixx](https://github.com/metagoto/fcgixx). And considering http, it could perhaps be valuable to look at SPDY / HTTP 2.0, because even if it will be as compatible as possible with HTTP 1.1 I believe that features like server push transactions should be taken into account in your library API. As you spoke about websockets you should have thought to something similar. You spoke about embedded, having facilities or an API which abstracts protocols like CoAP translation from/to HTTP would also be nice in my opinion. Cheers, -- Damien Buhl Em Sáb, 2014-03-01 às 11:46 +0000, Niall Douglas escreveu:
Algorithmically an async HTTP server is not challenging.
Yes, I know that. The most challenging part in a HTTP server (in my opinion) is the interface, not event the implementation. That's why I'm considering WebSocket support too, but I have to investigate further about the full scope of the proposal.
Look into Python's Twisted. Do what they do.
I studied several web solutions to serve as inspiration, but I haven't checked Python's Twisted or Boost.AFIO. I'll surely check them now. Thanks for pointing me them out. It may improve my proposal already. :)
Disclaimer: I designed proposed Boost.AFIO.
Then I know who I shall bug for questions. :) -- Vinícius dos Santos Oliveira https://about.me/vinipsmaker
Em Seg, 2014-03-03 às 08:20 +0100, Damien Buhl escreveu:
Hi Vinícius,
Hi Damien, thanks for the feedback. And you write emails like MarkDown(?).
Perhaps it's not bad to look at what Artyom Beilis does with cppcms : [http://cppcms.com/wikipp/en/page/main ](http://cppcms.com/wikipp/en/page/main)
I'm familiarized with cppcms. The author wrote nice benchmark projects/texts[1][2] that inspired me to try to achieve the same some day.
And others things like [https://github.com/metagoto/fcgixx](https://github.com/metagoto/fcgixx).
I just did a fast incautious read through the project now that you mentioned. It looks like it won't serve as inspiration to a generic project like I want, but more like an implementation thing. I'll check it appropriately and maybe comment more later anyway.
And considering http, it could perhaps be valuable to look at SPDY / HTTP 2.0, because even if it will be as compatible as possible with HTTP 1.1 I believe that features like server push transactions should be taken into account in your library API. As you spoke about websockets you should have thought to something similar.
Yes, there was an interesting talk about HTTP/2.0 on linux.conf.au[3] that I watched (thanks to the provided online records) several weeks ago and I'll of course take that in account in my proposal.
You spoke about embedded, having facilities or an API which abstracts protocols like CoAP translation from/to HTTP would also be nice in my opinion.
I've never read about CoAP. Thanks for bringing this up. I'll check it out. [1] http://cppcms.com/wikipp/en/page/benchmarks_php [2] http://cppcms.com/wikipp/en/page/benchmarks_all [3] http://mirror.linux.org.au/linux.conf.au/2014/Wednesday/51-HTTP2.0_And_You_-... -- Vinícius dos Santos Oliveira https://about.me/vinipsmaker
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, everyone who knows the OptSolve++, I want to get the old versons of this really in an urgency. Can anyone help me? Best Max On 03/03/2014 09:06 AM, Vinícius dos Santos Oliveira wrote:
Em Seg, 2014-03-03 às 08:20 +0100, Damien Buhl escreveu:
Hi Vinícius,
Hi Damien, thanks for the feedback. And you write emails like MarkDown(?).
Perhaps it's not bad to look at what Artyom Beilis does with cppcms : [http://cppcms.com/wikipp/en/page/main ](http://cppcms.com/wikipp/en/page/main)
I'm familiarized with cppcms. The author wrote nice benchmark projects/texts[1][2] that inspired me to try to achieve the same some day.
And others things like [https://github.com/metagoto/fcgixx](https://github.com/metagoto/fcgixx).
I just did a fast incautious read through the project now that you mentioned. It looks like it won't serve as inspiration to a generic project like I want, but more like an implementation thing. I'll check it appropriately and maybe comment more later anyway.
And considering http, it could perhaps be valuable to look at SPDY / HTTP 2.0, because even if it will be as compatible as possible with HTTP 1.1 I believe that features like server push transactions should be taken into account in your library API. As you spoke about websockets you should have thought to something similar.
Yes, there was an interesting talk about HTTP/2.0 on linux.conf.au[3] that I watched (thanks to the provided online records) several weeks ago and I'll of course take that in account in my proposal.
You spoke about embedded, having facilities or an API which abstracts protocols like CoAP translation from/to HTTP would also be nice in my opinion.
I've never read about CoAP. Thanks for bringing this up. I'll check it out.
[1] http://cppcms.com/wikipp/en/page/benchmarks_php [2] http://cppcms.com/wikipp/en/page/benchmarks_all [3] http://mirror.linux.org.au/linux.conf.au/2014/Wednesday/51-HTTP2.0_And_You_-...
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJTFEE9AAoJEFXgJlQse3yYlSwH/R9hg/lBiNUl+QUPxW6QFuUV 3VnEoqnW6g7YOTV3ekHhx08X6SFp8W3wQGGF2CIrigjVCvU8WeZI9qGhOfJgR23V IXlI6NYF23u79om9Vzc7jIH3QU0lBTbMzbD535Usc5yh7o7TXxNjArPMFpDUXoQp DYs5LJDQ87saEW6i6H9U/qEB7Af9toy2ZNj6Ft+NevPg8SHQDmNpxKf8S18cye9w Sj7sg4uvXzs4qH5D0zCli67alD4Z8H3gANiHCJYOzfY7V9DOReE6RFZL16rqOSSU JiQp4kaGMeWW8ydvR7wV2DKMu/MB/scRtYwRrcF1Nh/58iEEVOKxISt453/DsDQ= =FV65 -----END PGP SIGNATURE-----
participants (3)
-
Damien Buhl -
Qingcao.Liu -
Vinícius dos Santos Oliveira