PEAK XOOPS - a happy side effect of D3 module 
I've just found Duplicatable V3 (D3) module is quite friendly multi core version!
Old Style module:
/var/www/xoops2.2/modules/(module)/LOGICS (core from xoops.org)
/var/www/xoops-jp/modules/(module)/LOGICS (core from xoopscube.jp)
/var/www/oreteki/modules/(module)/LOGICS (core from marijuana.ddo.jp)
Module developpers have to manage two directories.
This makes two problems hard to solve.
- .svn (or CVS)
- conflict
(symbolic link can't be usable for such a purpose)
D3 module:
/var/www/xoops2.2/modules/(module)/wrapper (core from xoops.org)
/var/www/xoops-jp/modules/(module)/wrapper (core from xoopscube.jp)
/var/www/oreteki/modules/(module)/wrapper (core from marijuana.ddo.jp)
/var/xoops_trust_path/modules/LOGICS
All you have to do is editing files under XOOPS_TRUST_PATH.
If you are a adminitrator of many sites in a server, you can enjoy the same merit.
When a D3 module is updated, you have to overwrite files just under XOOPS_TRUST_PATH once, even if you have 10 or 100 sites in the server 
- Compatibility between D3 and Cube2.1 (2006-07-19 05:05:52)
Comments list
gigamaster wrotes:
1) new user register
2) clone D3 module and rename to username
3) allow permissions only to this new user
This is the real "module for each user".
Today, I have to check the compatibility between 2.0.17 from xoosp.org and my modules.
It is quite easy for D3 modules because they are always "the latest version" though I don't use/update the file tree of 2.0.16 at all.
I'm bumping this to remember some friend developers how powerful is D3.
marco
I'm bumping this to remember some friend developers how powerful is D3.
And to remember another friend the cronjob example:
1) new user register
2) clone D3 module and rename to username
3) allow permissions only to this new user
Have Fun!
