All, I've removed support (well, it wasn't really supporting it anyway) for session-per-conversation in Tapernate. I would like to make it much more robust, allowing for "named" conversations. I need to figure out a nice, clean way to declare what conversation an action is supposed to take part in. Of course, we could declare an API like this:
conversationUtils.joinConversation( "updateMessage" ); conversationUtils.endConversation( "updateMessage" ); And, if you don't join a conversation, you just take part in the general conversation (which is only request-scoped). But, this would clutter up the code with these join/end conversation requests. I'd like to use annotations for this, but haven't come up with a nice way of doing so. I might be able to use an EnhancementWorker to do it. James --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
