Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Communication between modulesCommunication between modules
Previous
 
Next
New Post
7/19/2007 1:22 AM
 

Yes. Actually very happy to see it, too.


Vitaly Kozadayev
Principal
Viva Portals, L.L.C.
 
New Post
7/19/2007 3:05 AM
 

Help isnt using AJAX yet but it will.  I don't see any issues with it since the IMC works on load of the module so when we use an Update panel the module will reload each time.

Help shows you how to use IMC by itself.


Philip Beadle - Employee
 
New Post
7/22/2007 10:14 AM
 

Hi, someone working on my project found an article in China about the inter module communication I would appreciate comments.

I have read an article which is post in www.dnnchina.net ; the author is a DNN expert who has researched the internal communication between modules. Because this article has mentioned an issue about the internal communication between modules, so I have translated it and sent it to you in case you have not considered this issues before.

“After a period of time to research the DNN, I found the internal communication pattern of the DNN is not ideal. Because the communication pattern between the modules is kind of a pattern like broadcast, it will cause modules which have the listener refreshed at the same time. For example, There is a two communicators PA,PB, three listeners LA1,LA2,LB. our original expectation just want the event which is published by PA is only be listened by LA1,LA2. and the event which is published by PB is only be listened by LB. but real situation is that every time the communicator(for example PA) published the event, it will like the broadcast to sent the event to every listeners( LA1,LA2,LB) .It will cause the information are published everywhere, It will cause a lot issue of the web. The reason of the problem is that the ModuleCommunicate just connect all the communicators and listeners together, that is it. So we need to design and develop our own internal communication patterns for the modules, to just published the events to the listeners ,which we expect them to get the events.”
 
New Post
7/22/2007 11:30 AM
 


Does the "personalization" method suggested by Michael Washington's "Module Settings and Personalization: Easily Store Data for Your Module" require that the user be logged in?

 
New Post
7/22/2007 12:09 PM
 

kjparker wrote


Does the "personalization" method suggested by Michael Washington's "Module Settings and Personalization: Easily Store Data for Your Module" require that the user be logged in?

Yes it does and this can be frustrating because you usually like a consistent method to handle logged in users and non-logged in users. i usually use cookies for non logged in users.

The reason this is better than cookies for logged in users is because their settings stay the same when they are using a different computer.



Michael Washington
http://ADefWebserver.com
www.ADefHelpDesk.com
A Free Open Source DotNetNuke Help Desk Module
 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Communication between modulesCommunication between modules


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out