> For a system I'm working on I'm hoping to intercept the writing of files
> so it can be processed by a given other program.
> Because I am hoping to pass along some session parameters with the file
> hooking into the FSIO API probably isn't the right place to do this.
> Thus I suspect that using a module to implement our own command handlers
> is the right way to go here.
The FSIO API's write() callback would definitely be the right place for
what you want to do; anywhere else might see more data than just what is
written to disk. What sort of other session parameters are you hoping to
pass, along with the data being written?
Cheers,
TJ
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Much of your pain is self-chosen.
-Kahlil Gibran
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
------------------------------------------------------------------------------
Shape the Mobile Experience: Free Subscription
Software experts and developers: Be at the forefront of tech innovation.
Intel(R) Software Adrenaline delivers strategic insight and game-changing
conversations that shape the rapidly evolving mobile landscape. Sign up now.
http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk
_______________________________________________
ProFTPD Developers List
<proftpd-de...@proftpd.org>
https://lists.sourceforge.net/lists/listinfo/proftp-devel
