gemini+stream://

cage cage-dev at twistfold.it
Sat Aug 15 21:31:47 BST 2020


On Sat, Aug 15, 2020 at 07:59:18PM +0000, James Tomasino wrote:

Hi!!

> On 8/15/20 6:41 PM, cage wrote:
> > OK, my honest question  is now is: "is the last  point true?".  Let me
> > give you an example (sorry i have to talk about my work, i hope you do
> > not feel this annoying).

>  This was the  original point I missed as well  when I first started
> talking about  streaming in  Gemini. According to  the specification
> section 1.1, here's the transaction summary:

[...]

> Notice that final "Closes  connection" before "Handles response". If
> that  were  reversed  then  the protocol  would  effectively  assume
> everything was a stream and everyone's clients would be built in the
> manner  you've been  working toward.  Since it's  explicit that  the
> connection closes first in the  spec it's understandable that client
> authors built clients the way they have.

Thank  you  very  much!  Now  i understand  what  i  was  missing  and
everything is more clear!

Now i think it is better that  i think a bit about all the information
in this thread.

> Your technique  of treating everything  as a stream may  "just work"
> for gemini:// and gemini+stream:// both, honestly. Time will tell!

And, in the meanwhile, i have a lot of bugs to fix! :))

Bye!
C.


More information about the Gemini mailing list