engine communication with clients
- First Post
- Replies
- Stats
-
Go to
- ----- 2024 -----
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2023 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2022 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2021 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2020 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2019 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2018 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2017 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2016 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2015 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2014 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2013 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2012 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2011 -----
- December
- November
- October
Hello!
I have a question about communication between end users (clients) and
engine. From the documentation I see that it was planned to transfer
everything to REST API. Is it achieved already? Or do some types of
connection still use RPC protocol ( I know that engine and vdsm use
libvirt, but not sure about engine and clients).
Attachments:
- attachment.html (text/html — 377 bytes)
Hi!
We currently use a mix of REST and GWT-RPC for browser-server communication:
* most of the administration portal is implemented in GWT, and that part
uses GWT-RPC
* parts of the administration portal that are now broken out into not-GWT
components are using REST (migrate-vm functionality, more to come; the
dashboard uses its own custom REST endpoint via DashboadDataServlet)
* vm portal (ovirt-web-ui project) uses REST
Best wishes,
Greg
On Fri, May 11, 2018 at 10:38 AM, Anastasiya Ruzhanskaya <
anastasiya.ruzhanskaya(a)frtk.ru> wrote:
Hello!
I have a question about communication between end users (clients) and
engine. From the documentation I see that it was planned to transfer
everything to REST API. Is it achieved already? Or do some types of
connection still use RPC protocol ( I know that engine and vdsm use
libvirt, but not sure about engine and clients).
_______________________________________________
Devel mailing list -- devel(a)ovirt.org
To unsubscribe send an email to devel-leave(a)ovirt.org
--
GREG SHEREMETA
SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX
Red Hat NA
<https://www.redhat.com/>
gshereme(a)redhat.com IRC: gshereme
<https://red.ht/sig>
2377
days inactive
2387
days old
1 comments
2 participants
tags (0)
participants (2)
-
Anastasiya Ruzhanskaya -
Greg Sheremeta