‎03-10-2008 05:53 PM
‎03-11-2008 09:27 AM - edited ‎03-11-2008 09:28 AM
‎03-11-2008 11:47 AM
‎03-13-2008 08:02 PM
‎03-14-2008 10:44 AM - edited ‎03-14-2008 10:45 AM
@aartjan wrote:
Jim, there is no way I am not buying your new toolkit. I've been craving (ahhh) for that tool!
I realize my question was somewhat ambiguous, but at least now people can search for 'REST' and actually find something on this forum.
I want to give it a shot at some point. Running a http get call indeed is not such a big deal, but current NI tools will not support other REST commands (PUT, POST, DELETE). But really, I am just poking to see what happens here..
thanks guys
aartjan
‎12-17-2008 10:37 AM
Does anyone know if any of the other REST commands will be supported in the Internet Toolkit? I was looking at creating my own Twitter App, i can get the public timeline and my friend timeline etc but without POST I cannot update my status. I tried importing some of the open source DLL's that have been created but I can't get that working either.
Robin
‎12-18-2008
07:16 AM
- last edited on
‎05-04-2025
07:06 PM
by
Content Cleaner
Hi Roger,
As of LabVIEW version 8.6 there is build in support for some RESTful commands in the Web Services (you need at least a Full version of LabVIEW). I have been looking around and found the following pages from the LabVIEW 8.6 Help file:
LabVIEW Web Services (Windows)
Interacting with Web Method VIs (Windows)
Configure RESTful VI Dialog Box
I hope this will provide you with the requested information!
Good luck with your application.
Best regards,
Peter
‎12-18-2008 07:48 AM
Thanks for the info, but it seems that these are all about creating your own web service rather than talking to someone else's. The POST documentation is about receiving a post command and what to do with it.
Good reading though.
Robin
‎12-19-2008 05:16 AM
Hi Robin,
I have been checking out for information on the client side of RESTfull support within LabVIEW. There have been more requests about this and also a Product Suggestion has been created for this. This means the LabVIEW Developers might implement it in a later version of LabVIEW.
When this will be exactly, I cannot tell, since I don't know it as well.
We just have to wait until R&D will respond on this product suggestion.
Best regards,
Peter S
‎09-18-2009 08:53 AM
I noticed this was dated late 2008. I'm wondering if you've since found a solution. I too want to do POSTing, and client-side processing. Everything I've seen from labVIEW is from the server side. Since LabVIEW hasn't developed anything for client-side yet, how did you resolve this (hopefully you have). This is what I'm trying to figure out...Let me know if you have any thoughts. This is probably the third time I've posted this question, so I apologize.
What we have now is a server that (over secure link) sends html (web pages) to a client that (using Internet Explorer) displays these pages. The user enters button clicks, data, to command the server to do certain tasks. The server and client code were written by a third party. Now, WE are supposed to develop our own client such that the server (over this same secure link, using SSL/TLS) is going to send me XML instead of html. I'm supposed to parse this XML and generate a http request using POST method (I saw where LabVIEW Web Server uses PUT and DELETE) and the web server will respond with HTTPS containing XML response (etc). I plan on using easyXML from JKI Software to parse the XML, but that's about as far as I got. I think I need to use the TCP/IP Open Connection, etc to establish the server communication, but I'm not sure how to handle the secure-link aspects. I’ve seen mentioned using stunnel - I've also seen QT Framework, and Visual C++ suggested as I think it has similar MFC classes that support http implementation. To throw another variable into this ... I'm used to using TestStand to sequence through all my LabVIEW tests. I'm having a very difficult time conceptualizing (if that's a word) how this secure link is going to be "kicked off" by TestStand, but handled by LabVIEW and stunnel (or equivalent).