Hi professorcw1,

I've never had the need for IMC up until now (nice little example) - but can I have your thoughts on this please:

I have a Group Detail page. This is currently configured to receive an ID, or it shows a random or set group.

I then have numerous other Group lists (possible a Group search, or Groups by category etc) - I then make the Group Names clickable on all of these modules. These querystrings pass in a GroupID to the Detail page which is then displayed.

The key points here are that the Group Detail page does not care WHERE the querytstring is posted from. So I could make an a Href in an HTML module and say "View my Group" and the Detail page would receive it - I assume this is limitation of the IMC model? You need control over the Sender and Receiver? The module USerControls are also in different module definitions, so I have a module setting on each Sender module where you pick the Tab containing the Detail control, and this forms the NavigateURL (TabID) structure when I build the Group list.

Is this a candidate for IMC? Another example is that I have a search page that returns a Group CategororyID and a text search string. I currently pass these over as querystring params to the Search Results page that then executes the DB query and displays the results.

---

Entrepreneur

PokerDIY Tournament Manager - PokerDIY Tournament Manager<
PokerDIY Game Finder - Mobile Apps powered by DNN
PokerDIY - Connecting Poker Players

So in your first example, I would stick to the approach you are currently using.  The ability to access a group's detail page from a text module probably outweighs any IMC benefits.

With IMC you do need control over both the Sender (IModuleCommunicator) and Receiver (IModuleListener) implementations.  Your module code can easily handle this, but I'm not sure it's the best approach for your application.  With IMC you need to create separate module definitions (one module with multiple definitions) for each "view" key.  To accomplish this, you just create a module definition for your Sender and another for your Receiver.  You can then add a "settings" key to each.  In that regard, it's really no different than any other module that has multiple view controls.

Your search application is another one where, personally, I would stick with the querystring, unless you don't want people to have access to the criteria through the querystring.  There's usually no harm here, so I'd leave it alone.  That is an interesting idea, though.  I've actually never tried to use IMC across pages.  It seems there is always a better way to do that.  Several people have asked about that, though, so I'll give it a shot and see what happens.  Stay tuned.