One of the things about being on Channel9 and other similar sites is that I always have to know what other developers think before I embark on a big project. Also, since I picked up C# and .NET, something about the environment always has me pushing to find out what the best practices are before beginning on my own with something I haven’t done before.
Weird. I didn’t used to be like that. I usually solved these problems completely on my own, but now I’m always paranoid that I may not be doing it the best way.
Anyhow, a quick question..
Exporting data from a Web application to be used on other Web sites or desktop and mobile applications is a no-brainer for me, but what about the other way around? What if I have an application that must share data with an ASP.NET application?
I’m trying to give a desktop server application a Web front-end to allow users to check status remotely, configure it, and pull data from it. My data can be easily represented in simple XML in this case. SOAP is not important. I don’t necessarily need to pass objects back and forth, just data.
What are my best options? I’m using C# for the desktop server application and C#/ASP.NET for the Web application, although it would be nice to not be limited to just .NET on the Web application side.
Remoting, named pipes, and proprietary UDP and TCP solutions all came to mind. I’m thinking since objects aren’t important and it would be cool to not limit myself to .NET on both sides, remoting might be out. And I might want a “session-less” solution for efficiency since I’d be fetching data between Web page loads, which rules out TCP.
But, anyway, does anyone have any ideas or has implemented something like this before?
Thanks in advance!