[Mod_ftpd] Changes to use 'mod_ftpd' with Win32
urkle at outoforder.cc
Wed Oct 26 02:19:54 EST 2005
On Wed, 2005-10-26 at 08:21 +0200, Marlon van den Berg wrote:
> On Tuesday, October 25, 2005 6:32 PM, Edward rudd wrote:
> Yep I know, but in some cases good old *malloc* and *free* work faster and
> I'm always
> not sure when to use *apr_palloc*. I did see that you used it in function
> but won't this cause a high pool usage? I mean, function
> *ftpd_ascii_convert* might be called
> more then once when transferring a huge text file. Doesn't this mean that it
> keeps on
> claiming pool space more than once during the file transfer, because
> *apr_pool_destroy* is
> only called at the end of the transfer? Or am I missing something?
> This is the reason why I used good old *malloc* and *free* within
> *ftpd_ascii_convert* and
> not *apr_palloc*.
well, possibly.. or one can create a *subpool* to control the scope of a
pool. Eventually that whole function just needs to go away and be
replaced with an output filter once I figure how to get he data
transfers going through the filter chain. Then this will be a
non-issue. And it will allow me to do some more cool things like text
replacement, say, for welcome messages.. And to allow a bandwidth
control module to be added on.
> Best regards,
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.outoforder.cc/pipermail/mod_ftpd/attachments/20051026/4f2e045c/attachment.bin
More information about the Mod_ftpd