Alright .. I have the "MS SQL Demo" code all ported over and working in my proof of concept app.
I feel like I'm missing something crucial from an "understanding" standpoint.
I understand what "HttpUtils.PostString" does. I understand how to retrieve the "query" parameter on the other side.
What I don't quite understand is - where is the parameter name "query" set at?
What if I want ONE job to use "query" and another job to use a different parameter name? I don't see where this is set at. It isn't in the ServerURL being used, it isn't part of the parameters for the PostString method...
... and while I have you all here (hehhehee), what are you guys using for the passing of username and password in this sort of situation? Are you sending in plain text? So like:
HttpUtils.PostString("Job1", "http://localhost/login.aspx", "username|password")
... and you handle the splitting of the query value ...? Are you encoding the username|password string before sending (base64, etc)? Best practice ideas?
Thanks for the help!
I feel like I'm missing something crucial from an "understanding" standpoint.
I understand what "HttpUtils.PostString" does. I understand how to retrieve the "query" parameter on the other side.
What I don't quite understand is - where is the parameter name "query" set at?
What if I want ONE job to use "query" and another job to use a different parameter name? I don't see where this is set at. It isn't in the ServerURL being used, it isn't part of the parameters for the PostString method...
... and while I have you all here (hehhehee), what are you guys using for the passing of username and password in this sort of situation? Are you sending in plain text? So like:
HttpUtils.PostString("Job1", "http://localhost/login.aspx", "username|password")
... and you handle the splitting of the query value ...? Are you encoding the username|password string before sending (base64, etc)? Best practice ideas?
Thanks for the help!