From: gdiaz@9grid.es
To: 9fans@9fans.net
Subject: [9fans] store 9p session-only values using lib9p
Date: Wed, 11 Jun 2008 22:06:20 +0200 [thread overview]
Message-ID: <0c2d4885e85a65f8cb0fba1ed4d12336@9grid.es> (raw)
Hello
I've a 9p server implemented using lib9p which serves decoded files, for example, i have a base64 encoded file i want to read, but i want to decode it at the same time the client reads. Then i need to save two offsets, the one sent to the client corresponds to the decoded data, and i need other which correspond to the original data. (base64 is an example, rfc2047 codification is the main issue)
If i save the offset adjustment in f->aux or simmilar, i can calculate the real file offset on the next T-reads, but that will only work if one client reads it at one time.
could that value be saved for each session?
i would love to hear from other's experiences,
thanks,
gabi
next reply other threads:[~2008-06-11 20:06 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-11 20:06 gdiaz [this message]
2008-06-11 20:48 ` Russ Cox
2008-06-11 20:58 ` gdiaz
2008-06-11 23:44 ` erik quanstrom
2008-06-12 0:01 ` [9fans] upas/fs Russ Cox
2008-06-12 2:31 ` erik quanstrom
2008-06-12 2:59 ` Lyndon Nerenberg
2008-06-12 8:34 ` [9fans] store 9p session-only values using lib9p gdiaz
2008-06-12 10:04 ` erik quanstrom
2008-06-12 10:24 ` Fco. J. Ballesteros
2008-06-12 10:28 ` Fco. J. Ballesteros
2008-06-12 10:39 ` gdiaz
2008-06-12 10:43 ` Francisco J Ballesteros
2008-06-12 10:55 ` gdiaz
2008-06-12 11:04 ` Francisco J Ballesteros
2008-06-12 11:11 ` gdiaz
2008-06-12 17:16 ` lucio
2008-06-12 12:25 ` erik quanstrom
2008-06-12 12:32 ` erik quanstrom
2008-06-12 14:03 ` Francisco J Ballesteros
2008-06-12 14:25 ` erik quanstrom
2008-06-12 14:49 ` Fco. J. Ballesteros
2008-06-12 14:55 ` Fco. J. Ballesteros
2008-06-12 15:06 ` erik quanstrom
2008-06-12 17:12 ` lucio
2008-06-12 10:26 ` gdiaz
2008-06-12 11:09 ` erik quanstrom
2008-06-12 13:29 ` gdiaz
2008-06-12 14:10 ` Russ Cox
2008-06-12 14:10 ` erik quanstrom
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=0c2d4885e85a65f8cb0fba1ed4d12336@9grid.es \
--to=gdiaz@9grid.es \
--cc=9fans@9fans.net \
/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).