Last post Feb 23, 2006 03:53 PM by onyaktech
Feb 22, 2006 10:08 AM|rosenblumy|LINK
I am working on integrating a web service to read my data from. I would like to build this generic so that I can reuse it to hook in other WebServices at a later date. I was wondering if this should be developed as a provider or as a module. As we are
using it to retrieve and to write data it seems to be the job of a provider, but the DNN providers seem to be rooted to database integration and have methods that do not really fit what I need in my WebService. Can anyone give me any insight into this matter?
Feb 23, 2006 02:28 PM|DeveloperMCDBA|LINK
no one has responded to this, so I'm gonna go with my thoughts here since I've been pondering the same:
If you look at the current providers: Membership, HTMLEditor, etc., these are there to be a base proxy to a more specific provider and can be swapped out at run time for an alternate, more desired implementation.
A web service would just be a asmx in a desktopmodules folder as far as I'm concerned. It doesn't neccessarily have to hook into anything for interaction. Your service could very well, use the same dataproviders normal modules do.
I welcome comments from anyone more informed about this than I am. [:)]
Feb 23, 2006 03:53 PM|onyaktech|LINK
I've built several Web Services as DNN Modules and it works great. I have Windows applications that connect to them and interacts with the DNN Portal through the web service. I even have a few mobile applications connecting to DNN sites through web services
setup as Modules.
However, I never built a module that integrates with the Web Service module. I don't think I ever will since the DLL of a module I will need data from is in the Bin... so it's easier to just reference the other modules DLL and grab data from it. Unless..
I was building a Web Service that would be called from another DNN site. I forgot who it was... but I was talking to someone on these boards about this earlier this year and as far as I know they didn't have any problems and worked great.
The web services I built use the data providers of DNN and other modules, just the same as if you were building a normal module for DNN.