3 Replies Latest reply on Jun 15, 2006 7:10 PM by Gavin King

    Begin Conversation on GET, Questions

    ryan dewell Novice

      We use the begin-conversation-on-GET pattern extensively in our app -- typically when starting a conversation about a specific database object.

      The problem with this model is that we're effectively creating far too many unnecessary conversations as a user bounces around freeform in the web application UI.

      For example, there's no reason to have multiple conversations in a session ABOUT "editing product 123" (in our application).

      Besides making our UI flow terribly strict to cut down on conversation creation, are there any other solutions (current or planned)?