Re: [boost] DotNet FileSystemWatcher like library proposal.

Subject: Re: [boost] DotNet FileSystemWatcher like library proposal.
From: Stewart, Robert (Robert.Stewart_at_[hidden])
Date: 2010-05-03 06:48:25

Fernando Pelliccioni wrote:

[Please don't top post.]

> Eric.Malenfant_at_[hidden]> wrote:
> > De Scott McMurray:
> > > On 29 April 2010 23:43, Fernando Pelliccioni wrote:
> > > >
> > > > Basically the library monitors for file system changes
> > > > and notifiesthrowing events.
> > >
> > > I think that'd definitely be a worthy addition.
> > >
> > > I'm curious how you see the interface.  Perhaps something
> > > inspired by ASIO?
> >
> > In fact, I think that something for ASIO already exists. See this
> > thread: http://thread.gmane.org/gmane.comp.lib.boost.asio.user/2699/

> Really I didn't think to create the File System Monitor like an ASIO
> extension.
>
> The design of the library is not thinking like ASIO. The
> events and handlers system is implemented using Boost.Function.

Do you think that is a superior approach or just what had occurred to you?  If the latter, do you like the Asio approach better?

> Until today I did not know about the implementation of Boris.
> It would have been useful to know it.

That raises the question of how such tools should be managed.  Should there be a place in the Wiki to refer to things built atop Asio that others might find useful?  Should such tools be proposed, reviewed, and accepted as official parts of Asio?

_____
Rob Stewart                           robert.stewart_at_[hidden]
Software Engineer, Core Software      using std::disclaimer;
Susquehanna International Group, LLP  http://www.sig.com

IMPORTANT: The information contained in this email and/or its attachments is confidential. If you are not the intended recipient, please notify the sender immediately by reply and immediately delete this message and all its attachments. Any review, use, reproduction, disclosure or dissemination of this message or any attachment by an unintended recipient is strictly prohibited. Neither this message nor any attachment is intended as or should be construed as an offer, solicitation or recommendation to buy or sell any security or other financial instrument. Neither the sender, his or her employer nor any of their respective affiliates makes any warranties as to the completeness or accuracy of any of the information contained herein or that this message or any of its attachments is free of viruses.