15 Sep
2013
15 Sep
'13
11:06 a.m.
It seems to me that the issue could be fixed with a JSON or SOAP API built
into the portal
website.
That would allow end-users to update information on the portal using
scripts or whatever mechanism they liked. Also because the API is hooked
into the portal's backend, there's no need to have a separate mechanism or
script to sync everything up between the DNS server, portal, and the API,
like is required with the email bot.
Also, because the API wouldn't need to be stateful, standard load balancing
could allow for backup servers.
Just an idea,
Blaine, K1QV
On Fri, Sep 13, 2013 at 9:27 AM, <kb9mwr(a)gmail.com> wrote:
(Please trim inclusions from previous messages)
_______________________________________________
Thomas,
In lue of an email robot, what if you could submit data using curl?
I understand the you need, but I also understand how complex it could
be two run to update mechanisms
On Fri, Sep 13, 2013 at 02:28:08PM +0200, Thomas Osterried wrote:
We need the bot. We can't live with a web
frontend.
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net
http://www.ampr.org/donate.html