Begin Conversation on GET, Questions

rdewell Jun 12, 2006 4:30 PM

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)?

Ryan

1. Re: Begin Conversation on GET, Questions

gavin.king Jun 15, 2006 3:38 AM (in response to rdewell)

You could try using PAGE context, perhaps.
Actions
2. Re: Begin Conversation on GET, Questions

rdewell Jun 15, 2006 2:19 PM (in response to rdewell)

To clarify, @Begin a conversation in a PAGE scoped component during the GET? Wouldn't the PAGE scoped component get destroyed at the end of the lifecycle making it unavailable if the conversation is then carried out?

How are other folks handling this? This issue would come into play with any global navigation combined with conversation-on-GET, for example. Is it just becoming the best practice to let these conversations expire out?

Thanks,

Ryan
Actions
3. Re: Begin Conversation on GET, Questions

gavin.king Jun 15, 2006 7:10 PM (in response to rdewell)

You can manually pass state from PAGE context to CONVERSATION context. Look at how the booking demo passes SESSIOn scope state into the CONVERSATION context.
Actions

Go to original post