well, it seems that everyone agree that the decision what to add to the menu is the client responsibility. It means there is no additional work needed on the oVirt engine side - going to remove the feature page. ----- Original Message -----
From: "Christophe Fergeau" <cfergeau@redhat.com> To: "Michal Skrivanek" <michal.skrivanek@redhat.com> Cc: "Itamar Heim" <iheim@redhat.com>, "Tomas Jelinek" <tjelinek@redhat.com>, spice-devel@lists.freedesktop.org, "engine-devel" <engine-devel@ovirt.org>, "Marc-André Lureau" <mlureau@redhat.com> Sent: Monday, June 24, 2013 11:47:36 AM Subject: Re: [Engine-devel] [Spice-devel] SPICE Foreign Menu Using REST
On Mon, Jun 24, 2013 at 10:02:29AM +0200, Michal Skrivanek wrote:
I would agree as long as it is not hardcoded and can be change in some config file easily. We shouldn't wait for next RHEL release to do a little modification if possible. I think "owning" the menu in some form on RHEV-M side has an advantage of delivery synchronization.
This probably would also make things harder from a client documentation point of view. With something too generic, there's also always the risk that it becomes a way to add workaround for bugs, or that the menu starts containing things that would be better integrated in other places in the client, ...
Christophe