Changeset 197

Show
Ignore:
Timestamp:
04/11/06 13:10:01 (3 years ago)
Author:
bart
Message:

* Silenced the unlock function for win32 until a windows developer can

take a look at it.

* Updated the README a little more for the new control panel
* Added release notes for beta2
* Bumped up version to 0.9.5-beta2
* Released beta2

Files:

Legend:

Unmodified
Added
Removed
Modified
Copied
Moved
  • eaccelerator/trunk/ChangeLog

    r196 r197  
     12006-04-11  Bart Vanbrabant <bart.vanbrabant at zoeloelip.be> 
     2 
     3        * Silenced the unlock function for win32 until a windows developer can 
     4          take a look at it. 
     5        * Updated the README a little more for the new control panel 
     6        * Added release notes for beta2 
     7        * Bumped up version to 0.9.5-beta2 
     8        * Released beta2 
     9 
    1102006-04-09  Bart Vanbrabant <bart.vanbrabant at zoeloelip.be> 
    211 
     
    79882006-03-06  Bart Vanbrabant <bart.vanbrabant at zoeloelip.be> 
    8089 
    81         * Removed the old webui and made a new controlpanel en disassembler. 
     90        * Removed the old webui and made a new controlpanel and disassembler. 
    8291        * Added php api documentation 
    8392 
  • eaccelerator/trunk/NEWS

    r174 r197  
     1Apr 11, 2006 - Bart Vanbrabant 
     2---------------------------------- 
     3 
     4 * Released 0.9.5-beta2 
     5 
     6    There are some big changes in this beta:  
     7        - The shared memory functions, session handler and content cache are  
     8          disabled by default now. They are only used by a small amount of 
     9          users and they could allow local users to fill up the memory, if they 
     10          aren't secured properly. 
     11        - The old web control panel and the disassembler have been removed  
     12          from the code. They have been replaced with a set of php functions  
     13          that allow the same functionality to be implemented in a PHP script. 
     14          The control.php and the dasm.php files are such scripts. More  
     15          information about this can be found in the README. 
     16        - A lot of bugfixes which bring us closer to full PHP 5.1 support. 
     17    This version is already quite stable and some people are already using it 
     18    in production environments. Please test this beta2 as good and as much as 
     19    you can. If you find a bug, report it back to us on the website and if 
     20    possible add a small snippet of code so we can reproduce it. 
     21 
    122Feb 24, 2006 - Bart Vanbrabant 
    223---------------------------------- 
  • eaccelerator/trunk/README

    r178 r197  
    243243When you compile eAccelerator with --with-eaccelerator-disassembler you need  
    244244to place the dasm.php file also in the same directory as the control.php file. 
     245You can set the username and password needed to access this file at the top 
     246of the file. 
    245247 
    246248eAccelerator API 
    247249---------------- 
    248250 
    249 eaccelerator_put($key, $value, $ttl=0) 
    250   puts the $value into shard memory for $ttl seconds. 
    251  
    252 eaccelerator_get($key) 
    253   returns the value from shared memory which was stored by  eaccelerator_put() 
    254   or null if it is not exists or was expired. 
    255  
    256 eaccelerator_rm($key) 
    257   removres the $key from shared memory 
    258  
    259 eaccelerator_gc() 
    260   removes all expired keys from shared memory 
    261  
    262 eaccelerator_lock($lock) 
    263   creates a lock with specified name. The lock can  be  released  by  function 
    264   eaccelerator_unlock() or automatic on the end of request. 
    265   For Example: 
    266   <?php 
    267     eaccelerator_lock("count"); 
    268     eaccelerator_put("count",eaccelerator_get("count")+1)); 
    269   ?> 
    270  
    271 eaccelerator_unlock($lock) 
    272   release lock with specified name 
    273  
    274 eaccelerator_set_session_handlers() 
    275   install the eaccelerator session handlers. 
    276   Since PHP 4.2.0 you can install eaccelerator session handlers 
    277   in "php.ini" by "session.save_handler=eaccelerator". 
    278  
    279 eaccelerator_cache_output($key, $eval_code, $ttl=0) 
    280   caches the output of $eval_code in shared memory for $ttl seconds. 
    281   Output can be removed from cache by calling mmcach_rm() with the same $key. 
    282   For Example: 
    283   <?php eaccelerator_cache_output('test', 'echo time(); phpinfo();', 30); ?> 
    284  
    285 eaccelerator_cache_result($key, $eval_code, $ttl=0) 
    286   caches the result of $eval_code in shared memory for $ttl seconds. 
    287   Result can be removed from cache by calling mmcach_rm() with the same $key. 
    288   For Example: 
    289   <?php eaccelerator_cache_output('test', 'time()." Hello";', 30); ?> 
    290  
    291 eaccelerator_cache_page($key, $ttl=0) 
    292   caches the full page for $ttl seconds. 
    293   For Example: 
    294   <?php 
    295     eaccelerator_cache_page($_SERVER['PHP_SELF'].'?GET='.serialize($_GET),30); 
    296     echo time(); 
    297     phpinfo(); 
    298   ?> 
    299  
    300 eaccelerator_rm_page($key) 
    301   removes the page which was cached by eaccelerator_cache_page() with the same 
    302   $key from cache 
    303  
    304 eaccelerator_encode($filename) 
    305   returns the encoded bytecode of compiled file $filename 
    306  
    307 eaccelerator_load($code) 
    308   loads script which was encoded by eaccelerator_encode() 
     251API documentation can be found on this website: http://bart.eaccelerator.net/doc/phpdoc/ 
    309252 
    310253Contact us 
  • eaccelerator/trunk/eaccelerator_version.h

    r163 r197  
    11#ifndef EACCELERATOR_VERSION 
    2 #define EACCELERATOR_VERSION "0.9.5-dev
     2#define EACCELERATOR_VERSION "0.9.5-beta2
    33#endif 
  • eaccelerator/trunk/mm.c

    r193 r197  
    592592static int mm_do_unlock(mm_mutex* lock) { 
    593593  if (ReleaseMutex(g_lock.hMutex) == 0) { 
    594     return 0; 
     594      // Releasing the mutex doesn't seem to work under windows. It gives some 
     595      // extremely obscure error code. Locking seems to work though. Because this 
     596      // flood the error log of the win32 users we are not going to return 0 here 
     597      // until a windows dev has found the problem. 
    595598  } 
    596599  return 1;