My appointment应用点了Edit后的roundtrip分析

1. authorization check request
   GET /sap/fiori/cuscrmmycalendar/sap/opu/odata/sap/CRM_APPOINTMENT_SRV/EditAuthorizationCheck?ObjectGuid=guid’3440B5B1-6F66-1ED5-8BEB-A758FAFA33B7’ HTTP/1.1
   response:
   {“d”:{“EditAuthorizationCheck”:{"__metadata":{“type”:“CRM_APPOINTMENT_SRV.ActionResult”},“ActionSuccessful”:“X”,“Message”:""}}

2.a 拿ETAG request

sap/fiori/cuscrmmycalendar/sap/opu/odata/sap/CRM_APPOINTMENT_SRV/AppointmentSet(guid’3440B5B1-6F66-1ED5-8BEB-BE9CE64BF3E8’)
response:

2.b 拿appointment的attendee和attachment信息
sap/fiori/cuscrmmycalendar/sap/opu/odata/sap/CRM_APPOINTMENT_SRV/AppointmentSet(guid’3440B5B1-6F66-1ED5-8BEB-BE9CE64BF3E8’)?$expand=Attendee,AppointmentToAttachment

3.a 在appointment的attendee和attachment信息读取回来之后，在successHandler里再继续读note信息。3.a和2.b是串行的，即2.b执行完之后，才轮到3.a执行：

3.b 还是在appointment和attendee的信息读取回来之后，在successHandler里调用attachment view的bindElement方法：

这个方法会call到框架的createBindingContext，最终导致再trigger一个odata request：