| Summary: | [Protocol] Rename "rwt_shutdown" header | ||
|---|---|---|---|
| Product: | [RT] RAP | Reporter: | Ralf Sternberg <rsternberg> |
| Component: | RWT | Assignee: | Project Inbox <rap-inbox> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | ivan |
| Version: | 2.2 | ||
| Target Milestone: | 2.2 M1 | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | protocol | ||
|
Description
Ralf Sternberg
The "rwt_" prefix was introduced to correspond to "rwt_initialize" parameter. I agree with Ralf to rename it to "shutdown". In addition I'll propose to rename "rwt_initialize" parameter to "startup". > rename "rwt_initialize" parameter to "startup"
I'd agree to this renaming but I still wonder if we could get rid of this parameter entirely and discover the startup case by the missing request counter instead. Once we change the request counter to be incremented on the client, it would be "requestsCounter": 0.
What about sending a display destroy operation instead of the "shutdown" header? (In reply to comment #3) > What about sending a display destroy operation instead of the "shutdown" > header? For me this will make the things a little bit messy as such destroy operation will not be handled by corresponding LCA (DisplayLCA), but by LifeCycleServiceHandler (in case of shutdown the life cycle is not executed). (In reply to comment #4) > (In reply to comment #3) > > What about sending a display destroy operation instead of the "shutdown" > > header? > For me this will make the things a little bit messy as such destroy > operation will not be handled by corresponding LCA (DisplayLCA), but by > LifeCycleServiceHandler (in case of shutdown the life cycle is not executed). Agree. So let's rename it to "shutdown". As for the rwt_initialize header, we agreed to remove it later as part of bug 403653. Fixed in master with commit 78520251b0ac904c157b9324256bbb1488f1e6dd. |