Complete Raw/Goto and Download unification
Goto should be for "interactive" elements as they are -- in which case the response is that object directly (as it works now mainly). There is no option to inspect the protocol headers when using these functions.
Raw will be the wrapper for the retrieved elements -- as getEmail works. A Set?Response function will be needed to promote the real content into the response state. In this fashion the actual protocol headers and connection can be inspected as part of the return.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Drafting
- Series goal:
- None
- Implementation:
-
Implemented
- Milestone target:
-
cleanup-and-unification
- Started by
- e.mortoray
- Completed by
- e.mortoray
Related branches
Sprints
Whiteboard
Perhaps the "Raw" version could just be called "Get", that would distinguish it from "Goto" and provide a nicer naming convention ( GetEmail vs. RawGetEmail)
The basic support is implemented with many back-end changes. Any additional features could be done without modifying that backend now.
