On Friday 04 June 2004 14:09, Alex Romayev wrote:
> Hi Chris,
>
> I think this is an option that might work, however, a
> couple of questions:
> - Since request parameters are not available to to
> coplets, I assume it still isn't possible to use
> CForms for binding?
I did not find a way :-(
> - Again, assuming CForms binding cannot be use, I have
> about 15 parameters that I need to pass. Does this
> meant I have to create 15 attributes in coplet
> configuration, 15 events in bookmarks.xml, and 15
> entries in sitemap to pass "coplet/attribute" to the
> coplet, or have you been able to find a better way?
I'm using this feature to pass one value to many coplets...
You won't need 15 entries in the sitemap if you want to pass 15 attributes to
the coplet. You can use uris like
bookmark?coplet-att1=value&coplet-att2=value&coplet-att3=value&coplet-att3=value&coplet-att4=value&coplet-att5=value&coplet-att6=value&coplet-att7=value&coplet-att8=value&coplet-att9=value&coplet-att10=value&coplet-att11=value&coplet-att12=value&coplet-att1=value&coplet-att13=value&coplet-att14=value&coplet-att15=value&
in the sitemap. The bookmark action will generate a {uri} consisting of all
coplet events.
The values in the url must be uri-encoded and I don't know how big
internal cocoon url's can grow.
15 parameters are many, maybe the best thing would be to store them as session
attributes, using the session-propagator action or flowscript.
The bookmark feature would be useful for layout control.
The session-attr input module or flowscript could be used to retrieve those
values stored in the session.
I think this way CachingURICoplet's could still be used for cform's.
Note: I have not tried this myself. Do session-attr's survive between coplets?
--
lg, Chris
