Hey John, Thanks for the quick answer.
Yes, Magnolia uses only one openwfe engine at the moment. (Sometimes, we should maybe propose to use some external ones, I guess ..) The process we have at the moment is: - on activation request, look in the Content Repository to find which flow is associated to the activation - feed a startFlow command with the xml definition, stored in the repository itself - define some custom parameters, such as, the page to be activated. - tell the engine to start the flow If I turn on openwfe debug in the last step, I get the impression some kind of compilation is happening to turn the JDOM document to something useful for OpenWfe. I wonder if some kind of mapping, or caching could be used at this level. In a magnolia context, the cache could be cleared only if some new flow definition has been uploaded. Otherwise, all flows are static. In irbridge, (90% magnolia-based ...) on our regression testing we get some decent performance on multiple activation requests, and the server CPU usage is still very slow, but I feel like the response to the user could be improved. As you said, there should be an option to turn this on/off, since you may want to avoid caching on development instances. > I have to look at caching process definitions, early versions of > OpenWFE had that, but everybody was asking to turn it off (especially > on development/validation platforms). > So, is there any way to turn it back on ? :D Ready to help anytime. Please, tell me if you need more info. Regards, Niko ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ OpenWFE - Open source WorkFlow Engine OpenWFE-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openwfe-users
