Re: making FAM a required dependency
- From: Alan Horkan <horkana tcd ie>
- To: James Willcox <jwillcox cs indiana edu>
- Cc: desktop-devel-list gnome org
- Subject: Re: making FAM a required dependency
- Date: Mon, 30 Sep 2002 23:49:43 +0100 (BST)
For us lesser mortals who do not code in our sleep it would be very
helpful if people could expand acronyms at least once in a thread and not
automatically assume that everyone knows what you mean.
i probably should know and i probably could figure it out but you already
know and to you it is just a few extra keystrokes for you and whole lot of
searching for me (and others) so please do us all a favor and when you
first use an a TLA (Three Letter Acronym) expand it.
It only takes a little extra effort to make things less scary and more
inviting to newbies who hopefully will stick around long enough to make a
"your humble neophyte who aint stupid but aint no guru neither"
On 30 Sep 2002, James Willcox wrote:
> Date: 30 Sep 2002 13:33:07 -0500
> From: James Willcox <jwillcox cs indiana edu>
> To: gnome-vfs-list gnome org, desktop-devel-list gnome org
> Subject: making FAM a required dependency
> Hi all,
> gnome-vfs supports the monitoring of local files through FAM. This is a
> great feature, but currently it's not one we can depend on, since FAM
> support is optional. Consequently, if you want things to work as
> expected, you have to handle the situation where monitoring isn't
> supported by implementing your own monitoring stuff. I see at least 2
> ways to fix this problem.
> 1) Make FAM a required dependency for gnome-vfs
> 2) Implement a fallback monitoring impl. in gnome-vfs when FAM isn't
> available. (only for local files)
> IMHO, 1) is the best solution, assuming that FAM works on all the
> platforms we plan to support.
> desktop-devel-list mailing list
> desktop-devel-list gnome org
] [Thread Prev