Hi All,

If you don't know the listX module, my basic understanding is that It can be used to grab data from databases (via queries calles) and web services to create custom views and forms.  The basics of the module are very attractive to me for rapid development using web service data that drives DNN content via taxonomy and projects

My problem is that I don't want to call my web service directly in listX because I'd like to cache the data in my own object to prevent large numbers of calls to the web service (which has preformance issues).  I can access .NET runtime properties from listX, such as PortalSettings, PageSettings, Content Properties, System Properties, etc.  If I went this route, is there a simple way to include my own business logic into the DNN page at runtime without to much banging on the DNN structure?  One untested idea was to create a hidden module on pages where I need to run my business logic to cache or grab my cached webservice information and then pull it into the listX module but there is the user control heirarchey issue.  This seem sloppy anyways.  Though I'd like something that I could add different Business logic to different Tabs if possible.  How simple is this to do?

Another option, I was thinking, was to create my own web service (which I may be doing anyways regarding much of this data).  My web service would be programmed to call my business logic (which envolves me caching objects from my other web service call).  Then, my listX modules could call my custom web service.

Would either of these work or make sense?  Or should I go the doublicate data road and dump my taxonomy into DNN?  If so, how would you synchronize this data easily?

Somewhat complex but I'd appreciate the help.  This is my first DNN project.

Thanks,
Ben

I am using my vendors support for specifics on the module options on this.  But my question here has more to do with how DNN might allow me to turn my own provider classes into something I can access from the page objects, like Portal Settings.  In this way, it's not module specific and lends itself to be used by some third party modules and also custom built modules and processes.  Though, yes, my other option with using a web service is more specific to this 3rd party module, but that's really an asp.net question of best practices.  But, yes, I'll try to keep it more DNN basic topics in the future.

Thanks.