plone

Products.RobotsTool-3.0.2-4.lbn25.noarch
You can read more about robots.txt at: * http://www.google.com/bot.html * http://www.robotstxt.org/wc/exclusion-admin.html
Located in LBN / … / Plone and Zope / BastionLinux 19
Products.SecureMailHost-1.1.2-4.lbn25.noarch Located in LBN / … / Plone and Zope / BastionLinux 19
Products.Sessions-4.0-3.lbn19.noarch
Zope 2 session management.
Located in LBN / … / Plone and Zope / BastionLinux 19
Products.SimpleAttachment-4.4-1.lbn25.noarch
Several Plone products have a need to handle simple attachments: content types that do not have a workflow of their own but will reuse the permissions on their container. SimpleAttachment implements simple file and image attachment types that can serve this need.
Located in LBN / … / Plone and Zope / BastionLinux 19
Products.SingleKeywordWidget-1.0a1-1.lbn19.noarch
Products.SingleKeywordWidget
Located in LBN / … / Plone and Zope / BastionLinux 19
Products.StandardCacheManagers-3.0-1.lbn25.noarch
This package provides two cache managers for Zope 2. A RAMCacheManager and an Accelerated HTTP cache manager, which adds HTTP cache headers to responses. The following is intended for people interested in the internals of RAMCacheManager, such as maintainers. Introduction The caching framework does not interpret the data in any way, it acts just as a general storage for data passed to it. It tries to check if the data is pickleable though. IOW, only pickleable data is cacheable. The idea behind the RAMCacheManager is that it should be shared between threads, so that the same objects are not cached in each thread. This is achieved by storing the cache data structure itself as a module level variable (RAMCacheManager.caches). This, of course, requires locking on modifications of that data structure. Each RAMCacheManager instance has one cache in RAMCacheManager.caches dictionary. A unique __cacheid is generated when creating a cache manager and it’s used as a key for caches. Object Hierarchy RAMCacheManager RAMCache ObjectCacheEntries CacheEntry RAMCacheManager is a persistent placeful object. It is assigned a unique __cacheid on its creation. It is then used as a key to look up the corresponding RAMCache object in the global caches dictionary. So, each RAMCacheManager has a single RAMCache related to it. RAMCache is a volatile cache, unique for each RAMCacheManager. It is shared among threads and does all the locking. It has a writelock. No locking is done on reading though. RAMCache keeps a dictionary of ObjectCacheEntries indexed by the physical path of a cached object. ObjectCacheEntries is a container for cached values for a single object. The values in it are indexed by a tuple of a view_name, interesting request variables, and extra keywords passed to Cache.ZCache_set(). CacheEntry is a wrapper around a single cached value. It stores the data itself, creation time, view_name and keeps the access count.
Located in LBN / … / Plone and Zope / BastionLinux 19
Products.TALESField-1.1.3-1.lbn25.noarch
An Archetypes field that stores TALES Expressions
Located in LBN / … / Plone and Zope / BastionLinux 19
Products.TemplateFields-1.2.5-1.lbn25.noarch
Supplies an Archetypes field useful for editing and storing Zope Page Templates
Located in LBN / … / Plone and Zope / BastionLinux 19
Products.TemporaryFolder-4.0-2.lbn19.noarch
Zope 2 temporary folder support.
Located in LBN / … / Plone and Zope / BastionLinux 19
Products.TextIndexNG-3.4.14-1.lbn25.noarch
Features: * DocumentConverters * StemmerSupport for 13 languages * SimilaritySearch for english text (based on the Levenshtein distance) * NearSearch, * PluggableParsers * extended StopWords support * full integration in ZCatalog * TestFunctionality through ZMI * ExtensibleArchitecture * being MoreEfficient than the current !TextIndex * full globbing support (wildcard search) * NormalizationSupport (e.g. reducing accented characters to their base form) * full UnicodeAwareness * Relevance ranking of search results added. Searches are now ranked using an extended cosine measure. The cosine measure is based on a vector model and calculates the document "score" based on the frequency of the query terms inside the document result set. * Much faster phrase/near search: the old implementation of TextIndexNG had to perform a very expensive job at query time when phrase/near search was performed. Re-using the !WidCode module of !ZCTextIndex made this operation less expensive. * Left-truncation added: TextIndexNG can be configured creation-time time to support left-truncation (means you can search for "*suffix") Left-truncation is an option because this feature requires a second reverted index inside the lexicion and much more memory! * optional auto-expansion support: This optional feature allows you to get better search results when some of the query terms could not be found. The index expands a query term "foo" to "foo*" if there was no hit for "foo". This expansion is currently global for the index. This feature will be available on a per-query basis in a later version. (Auto-expansion will be extended in a later version to search for similiar terms) * improved HTML converter: now using Chris Withers "Strip-o-Gram" module instead of the Strip-Tag-Parser * added converter for text/sgml * Similarity search (soundex, metaphone, doublemetaphone) dropped and replace with a more general approach and language indepedant approach using the Levenshtein distance. * range searches like "Fi..Foo" * substring searches "substring"
Located in LBN / … / Plone and Zope / BastionLinux 19

« Previous 10 items Next 10 items » 1 ... 2329 2330 2331 2332 2333 2334 2335 ... 4849

Sections

Search results


	Copyright © 2000-2025 Corporation of Balclutha Inc. All rights reserved.