gemini+stream://

[cage]

On Fri, Aug 14, 2020 at 11:39:20PM +0000, James Tomasino wrote:

Hi!

Honestly i  fail to understand  why a new  scheme is needed  here. The
protocol already supports  stream as discussed in  a previous messages
and i  do no  see a lott  of advantages for  using a  different scheme
except (as you wrote) to signal to  the user that the content will not
end.

Probably i am missing something, please help me to understand.

>  6. It is  still a single client-initiated request  happening in the
> foreground. We  aren't creating background threads  of who-know-what
> running services.  We're getting  an ongoing document  in real-time,
> that's all.

I do not think this is entirely  true if you want to update/keep alive
the  UI  of  the  client  while   the  content  is  flowing  from  the
server. Some kind of concurrent works enter in the equation, i think.

Bye!
C.