9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Jstsmthrgk <jstsmthrgk@jstsmthrgk.eu>
To: 9front@9front.org
Subject: [9front] Websocket Message Delimiters
Date: Sat, 12 Dec 2020 13:47:43 +0100	[thread overview]
Message-ID: <ad0f4853-7fef-34e5-898c-fb8becc8637c@jstsmthrgk.eu> (raw)

I have recently been thinking about writing a websocket implementation
for plan9/9front. I kind of wanted it to work similar to tcpsrv and
tcpclient.

Whatever, I want to be able to just put it on stdin/stdout of e.g.
exportfs, but also preserve message delimiters in some way.

The problem is that websocket allows message lenghts of up to 64^2-1,
which will definitely not work with single writes.

Does anyone know of any other option than implementing it as a tcp-like
stream and dropping message delimiters?

As for why I want to make it, I want to be able to make services that
are interfaceable from browser javascript, maybe even a drawterm-web.



             reply	other threads:[~2020-12-12 12:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-12 12:47 Jstsmthrgk [this message]
2020-12-12 13:35 ` sirjofri

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ad0f4853-7fef-34e5-898c-fb8becc8637c@jstsmthrgk.eu \
    --to=jstsmthrgk@jstsmthrgk.eu \
    --cc=9front@9front.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).