Reply to thread

Message

<blockquote data-quote="samuel337" data-source="post: 11269" data-attributes="member: 10347">Matter of fact, I just did some brief research on events in .NET remoting, and it doesn't seem that hard after all... I can't guarantee that I can do it, but I'll definitely try. Here's an article I found on it: <a href="http://www.c-sharpcorner.com/Code/2003/Nov/RemotingEvents.asp" target="_blank">http://www.c-sharpcorner.com/Code/2003/Nov/RemotingEvents.asp</a>But you can of course, keep polling the plugin if you like.I will expose the whole GUIPropertyManager component - you can access the properties and edit them provided you know the tag (e.g. #currentmodule).STSC - I'll have a look at your problem this weekend.DanHarvey:upnp communication is via HTTP, so in that sense its like a web server. However, with .NET its easy to open a port and use it for communication (without all the web server stuff, e.g. authentication, server farming, configuration etc.). So it doesn't require a web server like IIS or apache.I'll expose my plugin as a web service later, but if you're going to be using a .NET language, I suggest communicating with the plugin via .NET remoting rather than web services. This way, it eliminates the middle-man (web service). Sam</blockquote>

[QUOTE="samuel337, post: 11269, member: 10347"] Matter of fact, I just did some brief research on events in .NET remoting, and it doesn't seem that hard after all... I can't guarantee that I can do it, but I'll definitely try. Here's an article I found on it: [url]http://www.c-sharpcorner.com/Code/2003/Nov/RemotingEvents.asp[/url] But you can of course, keep polling the plugin if you like. I will expose the whole GUIPropertyManager component - you can access the properties and edit them provided you know the tag (e.g. #currentmodule). STSC - I'll have a look at your problem this weekend. DanHarvey: upnp communication is via HTTP, so in that sense its like a web server. However, with .NET its easy to open a port and use it for communication (without all the web server stuff, e.g. authentication, server farming, configuration etc.). So it doesn't require a web server like IIS or apache. I'll expose my plugin as a web service later, but if you're going to be using a .NET language, I suggest communicating with the plugin via .NET remoting rather than web services. This way, it eliminates the middle-man (web service). Sam [/QUOTE]

Verification