Changes between Version 4 and Version 5 of AutoHardLinking


Ignore:
Timestamp:
2012-07-13T16:53:42+02:00 (2 years ago)
Author:
moo
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • AutoHardLinking

    v4 v5  
    11[[PageOutline]] 
    2 = Auto Hard Linking = 
     2= In cache "Hard Linking" = 
    33== The problem == 
    44Many of you run your own server/vps that install only 1 copy of each web applications under your server document root, while some other of you, the vhost provider, allow every user install their own copy. For example, [http://www.vbulletin.com/ vBulletin] may be installed under each user's vhost document root. This result in not only disk read/seek without XCache installed, but also consume huge memory for caching them with XCache installed. Most *.php file is bigger after compiled/cached. 
    55 
    66== The Solution == 
    7 XCache has introduced a way to solve this headache once and for all. This is called auto hard linking. Whatever it called, let's see what it does. 
     7XCache has introduced a way to solve this headache once and for all. This is called in cache hard linking. Whatever it called, let's see what it does. 
    88 
    99It's easier to demonstrate in PHP pseudo code. 
     
    3737== FAQ == 
    3838 * How about the !__FILE!__ and !__DIR!__ in *.php that [ticket:117 get cached]? Don't worry, i had a [changeset:662 back-patching] to fix it already. 
    39  * "I have hard link in filesystem, is !__FILE!__ ok?". Nope, not yet. But it is not necessary anymore. 
     39 * "I have hard link in filesystem, is !__FILE!__ ok?". Yes, since XCache 2.0.1