Hi folks,

I wasted this weekend trying to get rid of the WebUI.
I say wasted, because I shortsightedly broke trunk (see [TS-644])
with the changes done to proxymgmt/Main.cc and proxy/mgmt/web2/WebIntrMain.cc
http://svn.apache.org/viewvc?view=revision&revision=1059308
and the changes to proxy/mgmt/web2/WebHttpContext.* done here:
http://svn.apache.org/viewvc?view=revision&revision=1059430

There are two ways out (I can see), the simple one is:

svn merge -c -1059308 

to revert back to the state before my first change and either
start over again, or leave WebUI in for the time being, until
the next brave dares to venture into these lands.

The not so simple way is to selectively revert the files broken:

for f in proxy/mgmt/web2/WebIntrMain.cc proxy/mgmt/web2/WebIntrMain.h 
proxy/mgmt/web2/WebHttpContext.cc proxy/mgmt/web2/WebHttpContext.h ; do svn cp 
$url/$f@1059307 $f ; done
for f in proxy/mgmt/Main.cc proxy/mgmt/api/CfgContextImpl.cc 
proxy/mgmt/api/CfgContextImpl.h proxy/mgmt/api/CfgContextUtils.cc 
proxy/mgmt/api/CfgContextUtils.h proxy/mgmt/api/GenericParser.cc 
proxy/mgmt/api/INKMgmtAPIStub.cc proxy/mgmt/api/include/INKMgmtAPI.h 
proxy/mgmt/api/remote/APITestCliRemote.cc proxy/mgmt/cli2/ConfigCmd.cc  ; do 
svn merge -c -1059308 $f ; done 

and fix them. That is: concentrate the functionality needed
to to serve the aconf somewhere in proxy/mgmt and continue
continue purging all (that is not needed) from web2.

Given the experience with WebUI so far, I'm almost
leaning towards the first option.

Thoughs?

i

-- 
Igor Galić

Tel: +43 (0) 664 886 22 883
Mail: i.ga...@brainsware.org
URL: http://brainsware.org/

Reply via email to