Browsing projects by Tag(s)

Select a tag to browse associated projects and drill deeper into the tag cloud.

Showing page 10 of 12

WhirlyCache is a simple high performance in-process cache, comparable to EHCache and OSCache (but faster). It includes pluggable implementations (FastHashMap, ConcurrentHashMap) and eviction policies.

0
 
  0 reviews  |  0 users  |  16,343 lines of code  |  0 current contributors  |  Analyzed over 2 years ago
 
 

Wrapper for shared memory and locking functionality across different PHP extensions.

0
 
  0 reviews  |  0 users  |  1,040 lines of code  |  1 current contributor  |  Analyzed 3 days ago
 
 

A collection of reusable abstractions for enterprise application developer: caching, IoC, pagination, repository, application services, unit of work, background processing, exception trace policy, work item, etc. Integration with Unity 2.0, EntLib 5.0, ASP.NET MVC 3.0, WatiN 2.0, Memcached 1.4.5. Modular design for both .net 2.0 and .net 4.

0
 
  0 reviews  |  0 users  |  40,124 lines of code  |  1 current contributor  |  Analyzed 2 months ago
 
 

What's qUIpt?qUIpt is a small library that is capable of caching Javascript files inside the users browser - even if SSL is active. qUIpt helps the site owner by reducing traffic costs and the user with faster page loading. Developers by the way might want to check ... [More] https://groups.google.com/group/quipt How does it work?Quite simple It checks for the contents of window.name while your page is being loaded. If there's nothing inside the window.name cache the JS files defined by you are fetched via XHR The same happens if the users enters your site for the first time of his current browser session or if document.referrer is off-domain or empty After that the contents of window.name are being evaluated If the user requests the next page on your domain the JS files are directly taken from window.name - no more requests necessary Is this secure?Yep - if the user enters your site the first time the JS files are requested - no matter what's already inside window.name An attacker can't set window.name from other tabs the user might surf on parallely Click for happinessSources Example usage Feedback is always appreciated - especially in this very early stage of the project. [Less]

0
 
  0 reviews  |  0 users  |  158 lines of code  |  0 current contributors  |  Analyzed 1 day ago
 
 

This project does 2 major things: 1. It makes sure you include every css and js only once in every page you generate. This is very helpful when using templating, since you want to attach the template css to the template, but if you reuse the template the css will be called several times, not ... [More] necessarily causing any damage, but there is a slight performance hit, and problems in firebug (and we don't want that!) 2. If you set $GENERAL_CONFIG'aggregate' = true, then this code starts aggregating the css and js files into one large file. This helps decrease calls to http, really boosting up your site's performance. USAGE: 1. Create the cache table (see notices) 2. Create the code accessing the cache table, basically this is a class supporting the functions $db->GetCacheInfo, $db->SetCacheInfo, and $db->CreateCacheInfo. 3. require js_css_aggregator in your code, and either call js_include_once(), or css_include_once() as necessary. 4. to output the cache into your html, the code provides the global variables $all_js and $all_css, which you just echo in your html. To provide the best performace for your site, echo $all_css at the top of your html, and echo $all_js at the bottom of your html. NOTICES: 1. To use the aggregator you need the following db table: CREATE TABLE cache ( id int(11) NOT NULL auto_increment, cache_name varchar(100) collate utf8_unicode_ci NOT NULL, cache_content text collate utf8_unicode_ci NOT NULL, version varchar(100) collate utf8_unicode_ci NOT NULL, last_update datetime NOT NULL, last_update_unix bigint(20) unsigned NOT NULL default '0', PRIMARY KEY (id), UNIQUE KEY cache_name (cache_name) ) I didn't add the database code to the project yet because it is too customized for the project I wrote the aggregator for. So this google code is for php programmers not afraid to hack and customize code to fit their own projects. I am hoping that in the near future I will have a quiet weekend to turn this code into a closed component. 2. The code currently creates a different cache per page, but that is easily modifiable. 3. There is different code producing the js and css includes, but they are virtually identical, I will probably pretty up this code when I have the time. WISHLIST: 1. Wrap this code in a normal class to get rid of the horrible global variables. 2. Split the parameter $GENERAL_CONFIG'aggregate' into $GENERAL_CONFIG'js-aggregate' and $GENERAL_CONFIG'css-aggregate', so people can choose whether they want to aggregate js or css only. 3. Add the database code to the class so people don't have to write it themselves. 4. That someone would either volunteer to help me with this, or that someone will take this and rewrite it into something more useful for the community :) [Less]

0
 
  0 reviews  |  0 users  |  0 current contributors
 
 

AboutMongrel-ESI is an ESI Server built as a Mongrel::Handler. It uses ragel to implement a native ESI Parser and the ruby language to make it easy to run and install. ESI stands for Edge Side Include. Edge Side meaning as near as possible to your customers. Include because it's a set of ... [More] tags you include in your pages. Based on Mongrel, it is a light weight easy to install cache server that handles a subset of the ESI spec. It's parser is written using ragel, so it's fast and portable. SupportPlease feel free to ask questions or submit patches to the group Installsvn checkout http://mongrel-esi.googlecode.com/svn/trunk/ mongrel-esi or gem install mongrel_esi Configuration OverviewAs of version 0.4 configuration is handled very similar to mongrel. You can pass a -S option to have a special ruby script loaded that defines your own custom routing rules. Here's a simple example: ESI::Config.define(listeners) do|config| # define the caching rules globally for all routes, defaults to ruby config.cache do|c| #c.memcached do|mc| # mc.servers = ['localhost:11211'] # mc.debug = false # mc.namespace = 'mesi' # mc.readonly = false #end c.ttl = 600 end # define rules for when to enable esi processing globally for all routes config.esi do|c| c.allowed_content_types = ['text/plain', 'text/html'] #c.enable_for_surrogate_only = true # default is false end # define request path routing rules config.routes do|s| s.match( /content/ ) do|r| r.servers = ['127.0.0.1:4000'] end s.default do|r| r.servers = ['127.0.0.1:3000'] end end end Supported ESI Featuresesi:include src: source of fragment timeout: duration to wait for response alt: if primary src fails, try this url onerror: if src and alt fail, raise an exception unless this value is 'continue' esi:try esi:attempt esi:except esi:invalidate Only basic invalidation is supported when using memcached <!DOCTYPE INVALIDATION SYSTEM "internal:///WCSinvalidation.dtd"> HTTP_COOKIE variable (e.g. $(HTTP_COOKIE{name}) will be replaced with the value of the cookie, name) From esi-lang + Inclusion - ESI can compose pages by assembling included content, which is fetched from the network. This allows each such fragment to have its own metadata (e.g., cacheability and handling information) seperately associated. - Variable support - ESI 1.0 supports the use of variables based on HTTP request attributes in a manner reminiscent of the Common Gateway Interface. These variables can be used by ESI statements or written directly into the processed markup. - Conditional processing - ESI allows conditional logic with Boolean comparisons to be used to influence how a template is processed. + Exception and error handling - ESI provides for specification of alternate and default resources in a number of situations. Surrogate-Control Header. Using the Surrogate-Control response header you can enable or disable ESI processing. Also, you can tell mongrel-esi how long to cache the response body by setting Surrogate-Control: max-age=50, where 50 is measured in seconds. DocumentationRDoc Coverage Report InformativeRdocs ESI Lang ESI Arch HTTP Reading Setting up a Rails Project[ESI_and_Rails] BlogI post about progress occassionally on my blog idle-hacking [Less]

0
 
  0 reviews  |  0 users  |  13,232 lines of code  |  0 current contributors  |  Analyzed 13 days ago
 
 

当前最新版本为2.5.2。svn代码已经上传,有需要的同学可以直接下载使用maven来构建项目。 该项目是Memcache Java 客户端的实现 使用前先请下载帮助文档:在downloads中Memcached Client HandBook(特别注意对于第三方开源库版本依赖) ... [More] 具体的代码,文档,测试内容都在Downloads 中可以获得 《MemCached Cache Java 客户端优化历程.doc》将描述详细的封装和优化过程 有任何问题可以联系wenchu.cenwc@alibaba-inc.com Memcache Client for Java Wrap and Optimize whalin memcache client. Optimize SocketIOPool Operation. add keyset function and cluster support and localcache + memcache support if you have any question,you can contact with me :). Email:wenchu.cenwc@alibaba-inc.com [Less]

0
 
  0 reviews  |  0 users  |  6,956 lines of code  |  0 current contributors  |  Analyzed 38 minutes ago
 
 

The CSS Server-side Pre-processor adds nested selectors, server-side imports, constants, and variables to CSS. Includes a caching mechanism.

0
 
  0 reviews  |  0 users  |  0 current contributors  |  Analyzed 9 days ago
 
 

Data and cluster support for guice applications including a drop-in replacement for guice's servlet support. Consists of Modules: warp-servlet (+ web conversations) See the project homepage for docs and mailing list support at http://www.wideplay.com

0
 
  0 reviews  |  0 users  |  4,739 lines of code  |  0 current contributors  |  Analyzed 2 days ago
 
 

Cirrus-x (Cix) is an OpenSource toolkit for building cloud based internet components and solutions. Components or solutions built using it can run in the cloud, on individual internet based servers or on servers behind organisational firewalls. In fact these components can run across several layers ... [More] in a concurrent and distributed fashion if so desired. Cirrus-x can be used to build simple components or complex cloud based information systems. It includes built in redundancy and data replication with local or distributed memory caching. The implementation provides REST based data models and natively supports JSON along with basic feeds for all items stored in the repository. Further Cirrus-x obviates the need for the complex administration associated with replicated relational databases by including a fast replicated and distributed storage system. [Less]

0
 
  0 reviews  |  0 users  |  0 current contributors  |  Analyzed 8 days ago
 
 
 
 

Creative Commons License Copyright © 2013 Black Duck Software, Inc. and its contributors, Some Rights Reserved. Unless otherwise marked, this work is licensed under a Creative Commons Attribution 3.0 Unported License . Ohloh ® and the Ohloh logo are trademarks of Black Duck Software, Inc. in the United States and/or other jurisdictions. All other trademarks are the property of their respective holders.