Date Huang

thanks for advice! Is it good idea that I refer to `struct TORRENT_EXTRA_EXPORT mmap_disk_io` directly as example? https://github.com/arvidn/libtorrent/blob/RC_2_0/src/mmap_disk_io.cpp#L165 also need to consider your advice to avoid some bug

after some study, piece might contains two non-continuous blocks of disk. so i still need to allocate additional mem space to store and send out in `async_read` i think i...

Is there possible to return partial piece in async_read? I want to make sure every `disk_buffer_holder` will be continues part but it might not be whole piece in it.

got it thanks that means I need to create a buffer pool, threading pool, cache pool for this topic. but it seems every disk_buffer_holder will hold 0x4000 size buffer always...

if you will consider to expose disk_buffer_pool, it will be great to consider store_buffer also. but those two components are a little bit complex to use, so maybe need more...

althought i more like the old way, i only need to considert about "storage" rather than whole disk io including threading. haha

that is true. maybe we should have some advance example for this to guide us

If our custom async_read returns incorrect data to libtorrent, will libtorrent deal with it or set torrent to error state? If some buffer might in write buffer pool but not...

> > If our custom async_read returns incorrect data to libtorrent, will libtorrent deal with it or set torrent to error state? > > Neither actually. libtorrent will assume that...

If it isn't a near plan, maybe I should pause the project and wait for some C++ experts from my friends to help me.