NelsonT
03-25-2002, 09:59 PM
I saw the post by oSM.
http://webhostingtalk.com/showthread.php?s=&threadid=41378
They (iamhosted) develop the Windows-Based AP to access CPanel.
A new concept? I think there should be some people want to do this before. But concern about to be limited to one CP protocal, and hardly (or you said a lots of dirty work) extend to other CP. Whenever the CP make siginificant changes, you have to upgrade the AP.
In fact, I expected the HostGUI is one kind of such product with Linux/FreeBSD backend and Windows-client-AP frontend when I first time saw it from jaguarpc last year. Lately, they show more infos about HostGUI, I knew I'm wrong.
So if you think WHM/CPanel dominate most part of the market, you can begin to develop the Windows AP or Linux AP to control CPanel from your desktop, "not from the Browser". ( I don't think there are any big differences).
Which is the better way to control you website? The problem is identical to "you want to access web-based email or use the POP3 mail client AP?" It depends.
Let's back to my question, if the webhosting backend provide both the web-based control panel(frontend) and some protocals for non-browser AP to access, then we can give the customer ready-to-use frontend panel, and we can do or some s/w developers are willing to do the control-panel s/w.
If the webhosting backend protocals or API are public and well defined as RFC, the s/w developers can do one AP to fit every control panel, like CPanel/Ensim/Plesk/IIS-related....
Since webhosting industry has been out for more than 5 years, there should be something like Open-Source control panel(webcp) and open source webhosting frontend/backend protocals.
http://webhostingtalk.com/showthread.php?s=&threadid=41378
They (iamhosted) develop the Windows-Based AP to access CPanel.
A new concept? I think there should be some people want to do this before. But concern about to be limited to one CP protocal, and hardly (or you said a lots of dirty work) extend to other CP. Whenever the CP make siginificant changes, you have to upgrade the AP.
In fact, I expected the HostGUI is one kind of such product with Linux/FreeBSD backend and Windows-client-AP frontend when I first time saw it from jaguarpc last year. Lately, they show more infos about HostGUI, I knew I'm wrong.
So if you think WHM/CPanel dominate most part of the market, you can begin to develop the Windows AP or Linux AP to control CPanel from your desktop, "not from the Browser". ( I don't think there are any big differences).
Which is the better way to control you website? The problem is identical to "you want to access web-based email or use the POP3 mail client AP?" It depends.
Let's back to my question, if the webhosting backend provide both the web-based control panel(frontend) and some protocals for non-browser AP to access, then we can give the customer ready-to-use frontend panel, and we can do or some s/w developers are willing to do the control-panel s/w.
If the webhosting backend protocals or API are public and well defined as RFC, the s/w developers can do one AP to fit every control panel, like CPanel/Ensim/Plesk/IIS-related....
Since webhosting industry has been out for more than 5 years, there should be something like Open-Source control panel(webcp) and open source webhosting frontend/backend protocals.