9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Einar Karttunen <ekarttun@cs.helsinki.fi>
To: Plan9 ML <9fans@cse.psu.edu>
Subject: [9fans] tcs and many channels
Date: Wed, 10 Mar 2004 13:17:19 +0200	[thread overview]
Message-ID: <20040310111719.GA9327@melkki.cs.Helsinki.FI> (raw)

Hello

I am hacking irc support to acme. I was wondering what would be the best
way to perform the charset conversion. Irc is quite broken, most
channels use legacy encodings, which are specified only implicitely. 

Now given a scenario with 30 channels, what would be a good way to
convert the data streams from the legacy codings to utf? The simple
solution would be to run one tcs for input and an another for output for
each channel. This would mean 60 tcs processes (and 30mb of ram).

The second approach would be to have one tcs process for each channel
for input and run a tcs process each time the user says something.
This would need half the memory, but would incur more overhead/line.

Is there a good solution to this? (Other than changing irc...)

- Einar Karttunen


             reply	other threads:[~2004-03-10 11:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-10 11:17 Einar Karttunen [this message]
2004-03-10 21:11 ` rog
2004-03-11  0:27 YAMANASHI Takeshi
2004-03-11  1:13 ` Kenji Okamoto
2004-03-11  1:43 YAMANASHI Takeshi

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=20040310111719.GA9327@melkki.cs.Helsinki.FI \
    --to=ekarttun@cs.helsinki.fi \
    --cc=9fans@cse.psu.edu \
    /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).