diff options
author | Loïc Hoguin <[email protected]> | 2016-08-29 12:39:49 +0200 |
---|---|---|
committer | Loïc Hoguin <[email protected]> | 2016-08-29 12:40:03 +0200 |
commit | c807880f7ac73f813b2660ea81a00f7712a4e793 (patch) | |
tree | ba1d09e9b177f230665a80513b33fbd532000ce4 /archives/extend/attachments/20130213 | |
parent | b1df25a7d9cda697513650659b781b55b40898f8 (diff) | |
download | ninenines.eu-c807880f7ac73f813b2660ea81a00f7712a4e793.tar.gz ninenines.eu-c807880f7ac73f813b2660ea81a00f7712a4e793.tar.bz2 ninenines.eu-c807880f7ac73f813b2660ea81a00f7712a4e793.zip |
Add old mailing list archives
Diffstat (limited to 'archives/extend/attachments/20130213')
-rw-r--r-- | archives/extend/attachments/20130213/41b12a6d/attachment.html | 50 | ||||
-rw-r--r-- | archives/extend/attachments/20130213/a992c0b6/attachment.html | 25 |
2 files changed, 75 insertions, 0 deletions
diff --git a/archives/extend/attachments/20130213/41b12a6d/attachment.html b/archives/extend/attachments/20130213/41b12a6d/attachment.html new file mode 100644 index 00000000..aa578a68 --- /dev/null +++ b/archives/extend/attachments/20130213/41b12a6d/attachment.html @@ -0,0 +1,50 @@ +<tt> +<p>Great news! </p><br> +<p>Congrats! </p><br> +<div class="gmail_quote">On Feb 12, 2013 11:36 AM, "Lo�c Hoguin" <<a href="mailto:[email protected]">[email protected]</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br> +Hello there!<br><br> +<br><br> +Cowboy 0.8 has been released. Cowboy is a small, fast and modular HTTP, REST and Websocket server.<br><br> +<br><br> +� <a href="https://github.com/extend/cowboy/" target="_blank">https://github.com/extend/<u></u>cowboy/</a><br><br> +<br><br> +The number of contributors who helped make this release considerably increased. Cowboy is available thanks to the code contributions from 50 users, double from the last release where 25 contributed.<br><br> +<br><br> +The number of users has also greatly increased. Cowboy is being used in ad bidding, set-top boxes, live TV events, content streaming services, and many more exciting areas.<br><br> +<br><br> +This new version has many highlights. You can take a look at the changelog for detailed information about the many changes.<br><br> +<br><br> +� <a href="https://github.com/extend/cowboy/blob/master/CHANGELOG.md" target="_blank">https://github.com/extend/<u></u>cowboy/blob/master/CHANGELOG.<u></u>md</a><br><br> +<br><br> +Cowboy scalability has been greatly improved in this version. This has been observed many times in production, including in the AdGear Tracker project (<a href="http://ferd.ca/rtb-where-erlang-blooms.html" target="_blank">http://ferd.ca/rtb-where-<u></u>erlang-blooms.html</a>) where updated nodes were able to handle 2 times more requests compared to older nodes. This improvement cannot be observed in "hello world" types of benchmarks. An article will soon be published to explain the reasons for this.<br><br> +<br> +<br><br> +Cowboy now features a brand new user guide. It is still a work in progress, so please open a ticket on Github if something is missing or incorrect.<br><br> +<br><br> +� <a href="http://ninenines.eu/docs/en/cowboy/HEAD/guide/introduction" target="_blank">http://ninenines.eu/docs/en/<u></u>cowboy/HEAD/guide/introduction</a><br><br> +<br><br> +Remaining work before 1.0 include REST improvements and SPDY support. The rest of the API should now be very close to stable.<br><br> +<br><br> +I am looking for a good writer who would like to co-author a Cowboy book. The book will be accessible to people who don't know Erlang but will also contain everything there is to know about Cowboy, making it suitable for both beginners and experts. Contact me if you are interested.<br><br> +<br> +<br><br> +I now take donations in addition to commercial support options, to allow individual users to help the project stay alive and kicking.<br><br> +<br><br> +� <a href="http://ninenines.eu/support" target="_blank">http://ninenines.eu/support</a><br><br> +<br><br> +Hope you enjoy it. As always, please send me as much feedback as possible to help me improve things even more, preferrably through Github tickets if it's related to code or documentation.<br><br> +<br><br> +Thanks for reading.<br><br> +<br><br> +-- <br><br> +Lo�c Hoguin<br><br> +Erlang Cowboy<br><br> +Nine Nines<br><br> +<a href="http://ninenines.eu" target="_blank">http://ninenines.eu</a><br><br> +______________________________<u></u>_________________<br><br> +erlang-questions mailing list<br><br> +<a href="mailto:[email protected]" target="_blank">[email protected]</a><br><br> +<a href="http://erlang.org/mailman/listinfo/erlang-questions" target="_blank">http://erlang.org/mailman/<u></u>listinfo/erlang-questions</a><br><br> +</blockquote></div><br> + +</tt> diff --git a/archives/extend/attachments/20130213/a992c0b6/attachment.html b/archives/extend/attachments/20130213/a992c0b6/attachment.html new file mode 100644 index 00000000..efa8eb31 --- /dev/null +++ b/archives/extend/attachments/20130213/a992c0b6/attachment.html @@ -0,0 +1,25 @@ +<tt> +<html><br> +<head><br> +<meta http-equiv="Content-Type" content="text/html; charset=us-ascii"><br> +</head><br> +<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif; "><br> +<div><br><br> +</div><br> +<div> In 6.1, and still in 8.0, there is some logic that surprised me, and I wanted to see if it was intentional, or if I'm missing something.</div><br> +<div><br><br> +</div><br> +<div> If I set up a POST such that it's a create, I get back a 303, rather than a 201, on successful create. This came as a bit of a surprise; I know from Webmachine, if it's a new resource being created, a POST will return a 201 (N11 to P11 in Webmachine's<br> + v3 diagram). </div><br> +<div><br><br> +</div><br> +<div> Is this intentional? The logic seems to be post_is_create/2 -> create_path/2 -> put_resource/3 -> choose_content_type/5 -> next/3 -> respond(_, _, 303). It may be that this is a better response, rather than a 201 with the location header, but it came<br> + as a surprise given web machine's behavior.</div><br> +<div><br><br> +</div><br> +<div> For background, I'm attempting to migrate some web machine code to Cowboy, which is serving a RESTful API to a Javascript client. The client is making CORS calls. Receiving a 303 and a Location header seemed to mean that the call was redirected before<br> + the client side code ever saw it (not sure what the browser was doing; I was expecting another request, but I wasn't quite lucid enough to check for that last night when working on it); a 201 allows me to examine the location. </div><br> +</body><br> +</html><br> + +</tt> |