Talk:Administration over HTTP: Difference between revisions
No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
==AJAX?== | ==AJAX?== | ||
--[[User:IJs|IJs]] 09:36, 9 May 2006 (CDT) - Reference has been placed. I assume nobody actually knows what AJAX is. | --[[User:IJs|IJs]] 09:36, 9 May 2006 (CDT) - Reference has been placed. I assume nobody actually knows what AJAX is. | ||
Besides, I think that the approach mentioned in the article (the part refering to AJAX) is way too professional and unnecessarily complex for a community development project (where developers from our community can participate.. a.k.a. Open Source). In order to make this project work, with "platforms" like AJAX, we will have to provide a base where third party people can build on, and I think that's a waste of our time. | |||
I would rather stick to simple and plain admin HTTP functionality that is, for example, provided by a PHP script on a separate webserver that speaks to the MTA server by using a special TCP port. The only thing we would need for that is TCP sockets functionality. The whole administration thing would, of course, be open-source. |
Revision as of 14:46, 9 May 2006
AJAX?
--IJs 09:36, 9 May 2006 (CDT) - Reference has been placed. I assume nobody actually knows what AJAX is. Besides, I think that the approach mentioned in the article (the part refering to AJAX) is way too professional and unnecessarily complex for a community development project (where developers from our community can participate.. a.k.a. Open Source). In order to make this project work, with "platforms" like AJAX, we will have to provide a base where third party people can build on, and I think that's a waste of our time.
I would rather stick to simple and plain admin HTTP functionality that is, for example, provided by a PHP script on a separate webserver that speaks to the MTA server by using a special TCP port. The only thing we would need for that is TCP sockets functionality. The whole administration thing would, of course, be open-source.