lgauthier Posted January 5, 2008 Posted January 5, 2008 This is essentially a long shot but it appears to me that a very powerful feature for ISY would be the ability to host web service (SOAP/HTTP) clients or consumers that could be triggered periodically in a program to retrieve info such as local weather conditions or eventually to communicate with utility companies or to send detailed alerts to home surveillance services. I have not yet done a full analysis of the possible solution but theoretically, one could supply the URL of the web service to the ISY program who would then get and analyze the WSDL and expose the parameters defined in the WSDL as parameters that could be set or queried by a program. Difficult to imagine a totally open-ended, general and "universal" (!) solution due to potential complexities of any given WSDL but there may be a possibility to define a few constraints that would make it possible for the ISY to interact with web services that follow or respect certain simple rules. Anyway, having the ISY capable of "pulling" or "pushing" information from/to virtually any server on the NET would be really cool! Comments welcome...
Mark Sanctuary Posted January 5, 2008 Posted January 5, 2008 I don't remember why but the UDI guys tested doing Atomic time server syncing and decided to remove it, but I just can't remember why now.
Michel Kohanim Posted January 6, 2008 Posted January 6, 2008 lgauthier, We are right there with you! The first thing we are doing is making ISY itself a fully WSDLized/DPWS (instead of UPnPelized) WebServices producer. And then, we'll be implementing web services interactions with ISY both as producers and consumers! In short, you are right on! Thanks so very much, With kind regards, Michel This is essentially a long shot but it appears to me that a very powerful feature for ISY would be the ability to host web service (SOAP/HTTP) clients or consumers that could be triggered periodically in a program to retrieve info such as local weather conditions or eventually to communicate with utility companies or to send detailed alerts to home surveillance services. I have not yet done a full analysis of the possible solution but theoretically, one could supply the URL of the web service to the ISY program who would then get and analyze the WSDL and expose the parameters defined in the WSDL as parameters that could be set or queried by a program. Difficult to imagine a totally open-ended, general and "universal" (!) solution due to potential complexities of any given WSDL but there may be a possibility to define a few constraints that would make it possible for the ISY to interact with web services that follow or respect certain simple rules. Anyway, having the ISY capable of "pulling" or "pushing" information from/to virtually any server on the NET would be really cool! Comments welcome...
rowland Posted January 6, 2008 Posted January 6, 2008 Michel, Are you planning on extending the ISY Program syntax and semantics to handle WSDL interfaces(portTypes)? I was unfamiliar WSDL until I saw this post. It seems to be a general framework that makes it possible to interface with web appliances, services, etc. that I've been talking about. A good introductory article on WSDL can be found at http://msdn2.microsoft.com/en-us/librar ... and_topic5
Michel Kohanim Posted January 6, 2008 Posted January 6, 2008 Rowland, Yes, precisely and thanks so very much for the link. With kind regards, Michel Michel, Are you planning on extending the ISY Program syntax and semantics to handle WSDL interfaces(portTypes)? I was unfamiliar WSDL until I saw this post. It seems to be a general framework that makes it possible to interface with web appliances, services, etc. that I've been talking about. A good introductory article on WSDL can be found at http://msdn2.microsoft.com/en-us/librar ... and_topic5
Recommended Posts
Archived
This topic is now archived and is closed to further replies.