gemini+submit:// (was Re: Uploading Gemini content)

[Sean Conner]

It was thus said that the Great Petite Abeille once stated:
> > On Jun 14, 2020, at 02:49, Petite Abeille <petite.abeille at gmail.com> wrote:
> > 
> > Considering the various network topology hurdles along the way, perhaps
> > the gemini protocol itself could facilitate such a role reversal by
> > offering a way to initiate such switch.
> 
> Perhaps this could be all done with just 1x (INPUT), between consenting
> pairs:
> 
> C: gemini://.../specification.gmi?⇄gemini://.../delta.txt --notify the server of the location of the delta and to switch role to get it, as indicated by the ⇄ sigil
> C⇄S: <start role reversal> -- the client maintain the network connection and accepts one gemini request
> S: gemini://.../delta.txt -- the server request the content from the client 
> C: 20 text/x-patch; length=4106 -- the client return the data to the server
> C⇄S: <end role reversal> -- upon EOF
> S: 30 gemini://.../specification.gmi -- client redirected to updated resource
> 
> This would require a persistent connection though. And some sort of
> indications of content EOF, be it length or otherwise.

  You know, another (maybe silly) way:

C: inimeg://example.com/specification.gmi CRLF
   <starts role reversal---the connection is maintained and the server sends the request>
S: gemini://example.com/specification.gmi CRLF
C: <data>
C: 20 text/gemini CRLF
   <end role reversal>
S: 31 gemini://example.com/spcification.gmi CRLF

  This doesn't solve the uploading of just data though.

  -spc