Hard-coding is in general a bad idea. From your standpoint, having a hard-coded username and password is like having no security at all.
I think we’re all on the same page about hard coding the password on the application… but is there another way to directly connect to a remote database, or should I have the client to make requests to a web api via https GET requests? Which of the two do you recommend?
···
On Tuesday, July 9, 2013 10:02:33 AM UTC-4, Boštjan Mejak wrote:
Hard-coding is in general a bad idea. From your standpoint, having a hard-coded username and password is like having no security at all.
I have often used xmlrpc for this purpose. It is very simple to code, and natural to use. If your usage will be small, you can use a cgi on the server side, but I recommend using wsgi behind either Apache or Nginx.
···
On Tue, Jul 9, 2013 at 10:29 AM, RedHotChiliPepper sharrukinjosephson@gmail.com wrote:
I think we’re all on the same page about hard coding the password on the application… but is there another way to directly connect to a remote database, or should I have the client to make requests to a web api via https GET requests? Which of the two do you recommend?
On Tuesday, July 9, 2013 10:02:33 AM UTC-4, Boštjan Mejak wrote:
Hard-coding is in general a bad idea. From your standpoint, having a hard-coded username and password is like having no security at all.
–
You received this message because you are subscribed to the Google Groups “wxPython-users” group.
To unsubscribe from this group and stop receiving emails from it, send an email to wxpython-users+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
–
Best Regards,
Michael Moriarity