Ignore:
Timestamp:
Jun 16, 2006 3:54:43 PM (18 years ago)
Author:
bennylp
Message:

Optimizations mostly in the conference bridge (gained more than 3x faster)

File:
1 edited

Legend:

Unmodified
Added
Removed
  • pjproject/trunk/pjlib/include/pj/doxygen.h

    r66 r513  
    3535 * @section intro_sec What is PJLIB 
    3636 * 
    37  * PJLIB is a small foundation library written in C for making scalable  
    38  * applications. Because of its small footprint, it can be used in embedded  
    39  * applications (we hope so!), but yet the library is also aimed for  
    40  * facilitating high performance protocol stacks. 
    41  * 
    42  * PJLIB is released under LGPL terms. 
     37 * PJLIB is an Open Source, small footprint framework library written in C for  
     38 * making scalable applications. Because of its small footprint, it can be used 
     39 * in embedded applications (we hope so!), but yet the library is also aimed for 
     40 * facilitating the creation of high performance protocol stacks. 
     41 * 
     42 * PJLIB is released under GPL terms. 
    4343 * 
    4444 * @section download_sec Download 
     
    5656 * @subsection doc_ver_subsec Version 
    5757 * 
    58  * This document corresponds to PJLIB version 0.3-pre2. 
     58 * This document corresponds to PJLIB version 0.5.6. 
    5959 * 
    6060 * 
     
    115115 * @subsection open_source_feat It's Open Source! 
    116116 * 
    117  * PJLIB is currently released on LGPL license. We may release PJLIB under 
    118  * additional schemes in the future (such as GPL or MPL) to incorporate 
    119  * linking with specific application, however, one thing for sure is 
    120  * we will NEVER be able to make PJLIB a proprietary software. 
     117 * PJLIB is currently released on GPL license, but other arrangements 
     118 * can be made with the author. 
    121119 * 
    122120 * @subsection extreme_portable_feat Extreme Portability 
     
    128126 * It can even run in environment where no ANSI LIBC is available.  
    129127 * 
    130  * Currently PJLIB is being ported to: 
    131  *  - x86, Win32 (Win95/98/ME, NT/2000/XP/2003, mingw). 
    132  *  - x86, Linux (user mode and as <b>kernel module</b>(!)). 
    133  *  - alpha, Linux 
    134  * And coming up: 
    135  *  - x86, eCos 
    136  *  - ultra-II, Solaris. 
    137  *  - powerpc, MacOS 
    138  *  - m68k, PalmOS. 
    139  *  - arm, PocketPC 
    140  * 
    141  * No other library is known to have this extreme portability! 
     128 * Currently PJLIB is known to run on these platforms: 
     129 *  - Win32/x86 (Win95/98/ME, NT/2000/XP/2003, mingw). 
     130 *  - arm, WinCE and Windows Mobile. 
     131 *  - Linux/x86, (user mode and as <b>kernel module</b>(!)). 
     132 *  - Linux/alpha 
     133 *  - Solaris/ultra. 
     134 *  - MacOS X/powerpc 
     135 *  - RTEMS (x86 and powerpc). 
     136 * 
     137 * And efforts is under way to port PJLIB on: 
     138 *  - Symbian OS 
     139 * 
    142140 * 
    143141 * @subsection small_size_feat Small in Size 
     
    152150 * For more info, please see @ref pj_config. 
    153151 * 
     152 * 
     153 * @subsection big_perform_feat Big in Performance 
     154 * 
     155 * Almost everything in PJLIB is designed to achieve the highest possible 
     156 * performance out of the target platform.  
     157 * 
     158 * 
    154159 * @subsection no_dyn_mem No Dynamic Memory Allocations 
    155160 * 
     
    165170 *    destroyed. 
    166171 * 
    167  * The performance gained on some systems can be as high as 10x speed up 
    168  * against \a malloc() and \a free(). 
     172 * The performance gained on some systems can be as high as 30x speed up 
     173 * against \a malloc() and \a free() on certain configurations, but of 
     174 * course your mileage may vary.  
    169175 * 
    170176 * For more information, see \ref PJ_POOL_GROUP 
     
    384390 * 
    385391 * You MUST NOT use \a malloc() or any other memory allocation functions. 
    386  * Use PJLIB pool instead! It's faster and most portable. 
     392 * Use PJLIB @ref PJ_POOL_GROUP instead! It's faster and most portable. 
    387393 * 
    388394 * @subsection logging_subsubsec Use Logging for Text Display 
    389395 * 
    390  * DO NOT use <stdio.h> for text output. Use PJLIB logging instead. 
     396 * DO NOT use <stdio.h> for text output. Use PJLIB @ref PJ_LOG instead. 
    391397 * 
    392398 * 
Note: See TracChangeset for help on using the changeset viewer.