From: Tiago Natel <tiago.natel@neoway.com.br>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] Fwd: lib9p: Add clunk callback to Srv struct
Date: Mon, 1 Feb 2016 19:54:58 -0200 [thread overview]
Message-ID: <CAEDK68av9j-vRwY0_J8bgzs2mVsvW-zFO1+2pWcc8zAwsmbUpA@mail.gmail.com> (raw)
In-Reply-To: <CAEDK68Ze=Di=8qQt1GOfkhq9nxb29=q=Z+AUuxzJouOT6_WeTg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 967 bytes --]
Someone here can help me?
---------- Forwarded message ----------
From: Tiago Natel <tiago.natel@neoway.com.br>
Date: 2016-02-01 19:17 GMT-02:00
Subject: lib9p: Add clunk callback to Srv struct
To: 9front@9front.org
Hello folks,
Is there a reason why lib9p doesn't have a clunk function pointer in Srv
struct?
I have a file server project using Srv and I want to know when no one
client have a specific file opened.
One way that I was able to get this working was forking 9front and adding a
clunk callback to Srv structure. See the commit below:
https://bitbucket.org/tiago4orion/plan9front/commits/5e1141f0a4aa98310cb0e2382c5c78c60fe73b4f
My project usage of the clunk routine is here:
https://bitbucket.org/tiago4orion/dchan/src/60dc3e45eb28c8a8289c177680120ef7f44e0925/fs.c?fileviewer=file-view-default#fs.c-680
This makes sense? Or is there better ways to achieve this?
And if that makes sense, it can go upstream?
Thanks.
[-- Attachment #2: Type: text/html, Size: 1698 bytes --]
next parent reply other threads:[~2016-02-01 21:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAEDK68Ze=Di=8qQt1GOfkhq9nxb29=q=Z+AUuxzJouOT6_WeTg@mail.gmail.com>
2016-02-01 21:54 ` Tiago Natel [this message]
2016-02-01 22:03 ` cinap_lenrek
2016-02-02 18:17 ` Tiago Natel
2016-02-02 19:15 ` Skip Tavakkolian
2016-02-03 1:25 ` cinap_lenrek
2016-02-03 11:53 ` Tiago Natel
2016-02-01 22:42 ` Skip Tavakkolian
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=CAEDK68av9j-vRwY0_J8bgzs2mVsvW-zFO1+2pWcc8zAwsmbUpA@mail.gmail.com \
--to=tiago.natel@neoway.com.br \
--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).