Sorry, this isn't much of a response. I don't know the answer to this
off the top of my head. I'll have to look at the code. Carsten is on
vacation for a few weeks and I didn't want to leave you hanging.
Ralph
Jean-Christophe Kermagoret wrote:
Hello,
Is there in the portal a way to create coplet instances in advance, to
reduce the first connection overhead ? A kind of coplet instance pool
that could be configured by profile ?
By the way, I saw in 2.1.8 the following configuration snippet in
cocoon.xconf, with coplet-factory, 'auto-create' and store attributes
that sound like keywords for me :-)
What is it for ?
<component
class="org.apache.cocoon.portal.coplet.impl.DefaultCopletFactory"
role="org.apache.cocoon.portal.coplet.CopletFactory">
<coplets>
<coplet
class="org.apache.cocoon.portal.coplet.CopletData"
name="standard">
<coplet-data-aspects>
<aspect
auto-create="true" class="java.lang.Boolean"
name="sizable" store="memory" value="true"/>
<aspect
auto-create="true" class="java.lang.Boolean"
name="mandatory" store="memory" value="false"/>
</coplet-data-aspects>
<coplet-instance-data-aspects>
<aspect
auto-create="true" class="java.lang.Integer"
name="size" store="session" value="1"/>
<aspect
auto-create="true" class="java.lang.Boolean"
name="fullScreen" store="temporary" value="false"/>
</coplet-instance-data-aspects>
</coplet>
</coplets>
</component>
Jean-Christophe
