Search results

Products.BeakerSessionDataManager-1.1-1.lbn25.noarch

Products.BeakerSessionDataManager is a replacement for the default Zope 2 session implementation. It uses Beaker as a backend (via collective.beaker) and adapts the Beaker session to provide the same interface as a normal Zope session. Beaker is a better alternative to the default session implementation for several reasons: * The Zope session implementation does not perform well in high-write scenarios. * Beaker provides better flexibility in where session data is actually stored. * Beaker is used and maintained outside of the Zope ecosystem.

Products.BlueAwstats-2.0-9.lbn13.noarch

BlueAwstats is a front-end for the third party software AWStats log file analyzer and statistics generator. AWStats itself consists of two parts: A log file analyzer to compute raw-statistical data and a renderer for websites. BlueAwstats is using the raw statistical data and replacing the html-renderer. BlueAwstats consists of three parts: 1. python module bda.awstatsparser to parse raw-data files generated by AWStats, see http://pypi.python.org/pypi/bda.awstatsparser 2. Zope Product BlueAwstatsMangementTool defines the settings i.e. the path to the awstats-raw-data on the filesystem and constraining the sites available. 3. CMF/Plone Product BlueAwstats to be placed as a tool in the Plone-site.

Products.BlueAwstats-2.0-9.lbn19.noarch

BlueAwstats is a front-end for the third party software AWStats log file analyzer and statistics generator. AWStats itself consists of two parts: A log file analyzer to compute raw-statistical data and a renderer for websites. BlueAwstats is using the raw statistical data and replacing the html-renderer. BlueAwstats consists of three parts: 1. python module bda.awstatsparser to parse raw-data files generated by AWStats, see http://pypi.python.org/pypi/bda.awstatsparser 2. Zope Product BlueAwstatsMangementTool defines the settings i.e. the path to the awstats-raw-data on the filesystem and constraining the sites available. 3. CMF/Plone Product BlueAwstats to be placed as a tool in the Plone-site.

Products.BlueAwstats-2.0-9.lbn25.noarch

BlueAwstats is a front-end for the third party software AWStats log file analyzer and statistics generator. AWStats itself consists of two parts: A log file analyzer to compute raw-statistical data and a renderer for websites. BlueAwstats is using the raw statistical data and replacing the html-renderer. BlueAwstats consists of three parts: 1. python module bda.awstatsparser to parse raw-data files generated by AWStats, see http://pypi.python.org/pypi/bda.awstatsparser 2. Zope Product BlueAwstatsMangementTool defines the settings i.e. the path to the awstats-raw-data on the filesystem and constraining the sites available. 3. CMF/Plone Product BlueAwstats to be placed as a tool in the Plone-site.

Products.BlueAwstatsManagementTool-2.0-3.lbn13.noarch

BlueAwstatsManagementTool is a products to manage access to the available statistics from AWStats on a Server. Added outside a plone site in the ZMI you can controll access to statistics in general. Installed Inside a plone site you have better abilities to control access to statistics on user level. There must be at least one Management Tool inside a zope instance to use BlueAwstats (and only one per folder level). The first one found by aquisition is used for the calling plone site.

Products.BlueAwstatsManagementTool-2.0-3.lbn19.noarch

BlueAwstatsManagementTool is a products to manage access to the available statistics from AWStats on a Server. Added outside a plone site in the ZMI you can controll access to statistics in general. Installed Inside a plone site you have better abilities to control access to statistics on user level. There must be at least one Management Tool inside a zope instance to use BlueAwstats (and only one per folder level). The first one found by aquisition is used for the calling plone site.

Products.BlueAwstatsManagementTool-2.0-3.lbn25.noarch

BlueAwstatsManagementTool is a products to manage access to the available statistics from AWStats on a Server. Added outside a plone site in the ZMI you can controll access to statistics in general. Installed Inside a plone site you have better abilities to control access to statistics on user level. There must be at least one Management Tool inside a zope instance to use BlueAwstats (and only one per folder level). The first one found by aquisition is used for the calling plone site.

Products.BTreeFolder2-2.13.4-2.lbn13.noarch

A BTree based implementation for Zope 2's OFS.

Products.BTreeFolder2-3.0-1.lbn25.noarch

BTreeFolder2 is a Zope product that acts like a Zope 2 OFS folder but can store many more items. When you fill a Zope folder with too many items, both Zope and your browser get overwhelmed. Zope has to load and store a large folder object, and the browser has to render large HTML tables repeatedly. Zope can store a lot of objects, but it has trouble storing a lot of objects in a single standard folder. Zope Corporation once had an extensive discussion on the subject. It was decided that we would expand standard folders to handle large numbers of objects gracefully. Unfortunately, Zope folders are used and extended in so many ways today that it would be difficult to modify standard folders in a way that would be compatible with all Zope products. So the BTreeFolder product was born. It stored all subobjects in a ZODB BTree, a structure designed to allow many items without loading them all into memory. It also rendered the contents of the folder as a simple select list rather than a table. Most browsers have no trouble rendering large select lists. But there was still one issue remaining. BTreeFolders still stored the ID of all subobjects in a single database record. If you put tens of thousands of items in a single BTreeFolder, you would still be loading and storing a multi-megabyte folder object. Zope can do this, but not quickly, and not without bloating the database. BTreeFolder2 solves this issue. It stores not only the subobjects but also the IDs of the subobjects in a BTree. It also batches the list of items in the UI, showing only 1000 items at a time. So if you write your application carefully, you can use a BTreeFolder2 to store as many items as will fit in physical storage. There are products that depend on the internal structure of the original BTreeFolder, however. So rather than risk breaking those products, the product has been renamed. You can have both products installed at the same time. If you’re developing new applications, you should use BTreeFolder2.

Products.BTreeFolder2-3.0-1.lbn25.noarch

BTreeFolder2 is a Zope product that acts like a Zope 2 OFS folder but can store many more items. When you fill a Zope folder with too many items, both Zope and your browser get overwhelmed. Zope has to load and store a large folder object, and the browser has to render large HTML tables repeatedly. Zope can store a lot of objects, but it has trouble storing a lot of objects in a single standard folder. Zope Corporation once had an extensive discussion on the subject. It was decided that we would expand standard folders to handle large numbers of objects gracefully. Unfortunately, Zope folders are used and extended in so many ways today that it would be difficult to modify standard folders in a way that would be compatible with all Zope products. So the BTreeFolder product was born. It stored all subobjects in a ZODB BTree, a structure designed to allow many items without loading them all into memory. It also rendered the contents of the folder as a simple select list rather than a table. Most browsers have no trouble rendering large select lists. But there was still one issue remaining. BTreeFolders still stored the ID of all subobjects in a single database record. If you put tens of thousands of items in a single BTreeFolder, you would still be loading and storing a multi-megabyte folder object. Zope can do this, but not quickly, and not without bloating the database. BTreeFolder2 solves this issue. It stores not only the subobjects but also the IDs of the subobjects in a BTree. It also batches the list of items in the UI, showing only 1000 items at a time. So if you write your application carefully, you can use a BTreeFolder2 to store as many items as will fit in physical storage. There are products that depend on the internal structure of the original BTreeFolder, however. So rather than risk breaking those products, the product has been renamed. You can have both products installed at the same time. If you’re developing new applications, you should use BTreeFolder2.