[dev] sesha status and questions

[Vilius Šumskas]

Sveiki,

Monday, January 16, 2012, 5:01:56 PM, you wrote:

>>> I haven't tested providing queues for whups from inventory yet. Is
>>> anybody of you using this in a real-world scenario and would like to
>>> help test? ;-)
>>> I think I can get a release candidate ready before H4.1.
>> That   could   be   interesting  feature for me. When ALPHA version is
>> ready I will try that.
> I just merged sesha into master branch. It's not released as "alpha" 
> yet. On first look the queue thing seems to work.
> When you want to test, edit this snippet into your registry.local.php

>      'sesha' => array(
>          'name' => _("Inventory"),
>      // Uncomment this line if you want Sesha to provide queue and version
>      // names instead of Whups:
>      // 'provides' => array('tickets/listQueues', 
> 'tickets/getQueueDetails', 'tickets/listVersions', 
> 'tickets/getVersionDetails'),
>          'menu_parent' => 'devel',
>      ),

Does  this  feature work in such a way, that every asset in sesha have
their  own  queue?  I have thousands of assets and a little bit afraid
about the server performance :)

Also  when  I  will  turn it on, what would happen to the old queues? Or do
they co-exist somehow?

-- 
Best regards,
 Vilius