Fooberichu described exactly what I do as well, I just don't deploy the changes.  (At least I don't think I do)  It has been a long time since I touched that module.

You could use the portal alias to build the URL automatically.

If the service might not exist, for proper coding, I would strongly recommend an enable/disable in the consuming application.

---

-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.


Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services

Rodney,

I think you need to step out of the box and make sure you understand exactly how people may want to use this in the future.  From what I gather, IMC is intended for when the modules exist on the same page or when Module "x" redirects to a tab that contains Module "y".  Fair enough.  But what happens when Module "x" doesn't exist on the same page as Module "y" or you don't want to redirect?  What about if somebody wanted to consume your API and publish events from a Desktop application?

I think a webservice will ultimately give you the most flexibility in how the API is consumed because it could be used by modules on the same page, different page, different server, etc.  You could allow mapping to the URL by "module instance" and/or override by a direct URL, for example, including any parameters necessary such as a module id, tab id, etc. 

You've probably seen these posts from a Google search, but here are a couple posts/tutorials treating the IMC topic:

http://www.kodhedz.com/Resources/DotNetNukeFramework/InterModuleCommunicationExample/tabid/38/Default.aspx

http://www.kemmis.info/blog/archive/2008/02/22/dotnetnuke-inter-module-communication-or-how-your-modules-can-get-their.aspx

With the web services you can either mimic or use the IWeb functionality to secure the service calls (I've mimicked the functionality in an app I'm writing, loving it).

---

-- Jon Seeley
DotNetNuke Modules
Custom DotNetNuke and .NET Development
http://www.seeleyware.com