Re: [dylan] Thinking about (functional, lazy) streams, networking and the future
Bruce Hoult <[email protected]> Mon, 28 Jul 2014 16:46:24 +1200
| Newsgroups | gmane.comp.lang.dylan.gwydion.devel |
|---|---|
| Message-ID | <CAMU+EkykDV4DButQk7o9_qiHn80e08OHN8kuVJSDQsBEtULQ8A@mail.gmail.com> |
--===============0196378053== Content-Type: multipart/alternative; boundary=e89a8ffbae41e9be0604ff399aee --e89a8ffbae41e9be0604ff399aee Content-Type: text/plain; charset=UTF-8 It would be useful for the API to have a "commit headers" call, signifying that there will be no further changes to headers (and attempting to do so will cause an exception). Typical web pages with a limited amount of data won't have to care. Clients that want to do things such as stream video or other large objects can send the headers as soon as they are ready. On Mon, Jul 28, 2014 at 9:08 AM, Scott McKay <[email protected]> wrote: > Yeah, interesting posts. > > Async streams with some sort of "promise" mechanism > might be good. > > Beware of not buffering HTTP results. IIRC, you run in to problems > if you partially generate a result, then get an error and decide you > need to go back and change a header once it's been sent. > > --S > > > > > > On Sat, Jul 26, 2014 at 8:20 AM, Bruce Mitchener < > [email protected]> wrote: > >> I've written a couple of blog posts: >> >> http://dylanfoundry.org/2014/07/25/beginning-to-rethink-streams/ >> http://dylanfoundry.org/2014/07/26/http-and-stream-processing/ >> >> I've posted the first one (so far) on a news aggregation site to see if >> there's interest there in having a discussion: >> >> https://lobste.rs/s/4jnuqd/beginning_to_rethink_streams >> >> I'd love to have some in depth discussions on this ... >> >> - Bruce >> >> >> _______________________________________________ >> hackers mailing list >> [email protected] >> https://lists.opendylan.org/mailman/listinfo/hackers >> >> > > _______________________________________________ > hackers mailing list > [email protected] > https://lists.opendylan.org/mailman/listinfo/hackers > > --e89a8ffbae41e9be0604ff399aee Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">It would be useful for the API to have a "commit head= ers" call, signifying that there will be no further changes to headers= (and attempting to do so will cause an exception).<div><br></div><div>Typi= cal web pages with a limited amount of data won't have to care. Clients= that want to do things such as stream video or other large objects can sen= d the headers as soon as they are ready.</div> </div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Mon,= Jul 28, 2014 at 9:08 AM, Scott McKay <span dir=3D"ltr"><<a href=3D"mail= to:[email protected]" target=3D"_blank">[email protected]</a>></span> wr= ote:<br> <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p= x #ccc solid;padding-left:1ex"><div dir=3D"ltr">Yeah, interesting posts.<di= v><br></div><div>Async streams with some sort of "promise" mechan= ism</div> <div>might be good.</div><div><br></div><div>Beware of not buffering HTTP r= esults. IIRC, you run in to problems</div> <div>if you partially generate a result, then get an error and decide you</= div><div>need to go back and change a header once it's been sent.</div>= <div><br></div><div>--S</div><div><br></div><div><br></div><div><br></div> </div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote"><div><d= iv class=3D"h5">On Sat, Jul 26, 2014 at 8:20 AM, Bruce Mitchener <span dir= =3D"ltr"><<a href=3D"mailto:[email protected]" target=3D"_blank"= >[email protected]</a>></span> wrote:<br> </div></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bo= rder-left:1px #ccc solid;padding-left:1ex"><div><div class=3D"h5"><div dir= =3D"ltr">I've written a couple of blog posts:<div><br></div><div>=C2=A0= =C2=A0<a href=3D"http://dylanfoundry.org/2014/07/25/beginning-to-rethink-st= reams/" target=3D"_blank">http://dylanfoundry.org/2014/07/25/beginning-to-r= ethink-streams/</a></div> <div>=C2=A0 <a href=3D"http://dylanfoundry.org/2014/07/26/http-and-stream-p= rocessing/" target=3D"_blank">http://dylanfoundry.org/2014/07/26/http-and-s= tream-processing/</a><br></div><div><br></div><div>I've posted the firs= t one (so far) on a news aggregation site to see if there's interest th= ere in having a discussion:<br> </div><div><br></div><div>=C2=A0 <a href=3D"https://lobste.rs/s/4jnuqd/begi= nning_to_rethink_streams" target=3D"_blank">https://lobste.rs/s/4jnuqd/begi= nning_to_rethink_streams</a></div><div><br></div><div>I'd love to have = some in depth discussions on this ...</div> <span><font color=3D"#888888"> <div><br></div><div>=C2=A0- Bruce</div><div><br></div></font></span></div> <br></div></div>_______________________________________________<br> hackers mailing list<br> <a href=3D"mailto:[email protected]" target=3D"_blank">hackers@li= sts.opendylan.org</a><br> <a href=3D"https://lists.opendylan.org/mailman/listinfo/hackers" target=3D"= _blank">https://lists.opendylan.org/mailman/listinfo/hackers</a><br> <br></blockquote></div><br></div> <br>_______________________________________________<br> hackers mailing list<br> <a href=3D"mailto:[email protected]">[email protected]<= /a><br> <a href=3D"https://lists.opendylan.org/mailman/listinfo/hackers" target=3D"= _blank">https://lists.opendylan.org/mailman/listinfo/hackers</a><br> <br></blockquote></div><br></div> --e89a8ffbae41e9be0604ff399aee-- --===============0196378053== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ hackers mailing list [email protected] https://lists.opendylan.org/mailman/listinfo/hackers --===============0196378053==--