y, May 15, 2012 4:08 AM
> To: cloudstack-users@incubator.apache.org
> Subject: RE: console proxy question
>
> Hi Kelven,
>
> Thank you for your efforts!
>
> Regards
>
> Tamas Monos D
question
The fix is not in 3.0.2 but I'll try to make it available in 3.0.3 release
Kelven
> -Original Message-
> From: Tamas Monos [mailto:tam...@veber.co.uk]
> Sent: Monday, May 14, 2012 11:04 AM
> To: cloudstack-users@incubator.apache.org
> Subject: RE: console pr
The fix is not in 3.0.2 but I'll try to make it available in 3.0.3 release
Kelven
> -Original Message-
> From: Tamas Monos [mailto:tam...@veber.co.uk]
> Sent: Monday, May 14, 2012 11:04 AM
> To: cloudstack-users@incubator.apache.org
> Subject: RE: console proxy que
Subject: RE: console proxy question
The decision of replacing with new VNC engine is primarily due to our shift to
ASF, previous console proxy uses third-party open source software that is not
compatible to ASF license policy.
The screen resolution problem has been fixed for certain hypervisors
rg
> Subject: console proxy question
>
> Dear All,
>
> I'm just having a thought about the console-proxy implementation in
> cloudstack.
> In 3.0.0 we had a console proxy that was able to follow screen resolution
> changes while from 3.0.1 upward this is gone.
> I
Dear All,
I'm just having a thought about the console-proxy implementation in cloudstack.
In 3.0.0 we had a console proxy that was able to follow screen resolution
changes while from 3.0.1 upward this is gone.
I saw on the devel list someone wrote/replaced the console-proxy part for some
reason.
