jmiven has quit [Quit: co'o]
jmiven has joined #ponylang
VexisArcanum has joined #ponylang
VexisArcanum has quit [Quit: Bye]
unbalanced has quit [Ping timeout: 264 seconds]
graaff has joined #ponylang
rurban has joined #ponylang
rurban has quit [Client Quit]
rurban has joined #ponylang
amclain has quit [Quit: Leaving]
rurban has quit [Quit: Leaving.]
rurban has joined #ponylang
Matthias247 has joined #ponylang
rurban1 has joined #ponylang
rurban has quit [Ping timeout: 258 seconds]
rurban1 has left #ponylang [#ponylang]
Matthias247 has quit [Read error: Connection reset by peer]
<
TwoNotes>
that is OK. Getting all this HTTP stuff working is going to take a while as well.
<
TwoNotes>
Big problem currently is that the existing 'pipelined request' mechanism is really in the way of doing proper streaming
<
TwoNotes>
Most browsers do not use pipelining - they just open multiple connections
_whitelogger has joined #ponylang
<
TwoNotes>
It looks like adding a flag to Server to disable pipeline ops (as is already done in Client) is the most straightforward
<
TwoNotes>
Well, MOST straight forward is just to rip out pipelining entirely, but I will take the more conservative approach for now
Matthias247 has joined #ponylang
graaff has quit [Quit: Leaving]
jemc has joined #ponylang
jemc has quit [Ping timeout: 248 seconds]
c355e3b has quit [Quit: Connection closed for inactivity]
jemc has joined #ponylang
jemc has quit [Ping timeout: 265 seconds]
<
TwoNotes>
I am fuzzy about what the capability on a fun definition does.
TwoNotes has left #ponylang [#ponylang]
jemc has joined #ponylang
<
doublec>
TwoNotes: It affects who can call the fun and what capability the 'this' in the fun is.
jemc has quit [Ping timeout: 246 seconds]