Details
-
Type: New Feature
-
Status: Resolved
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: EE-4.0.0.GA, 4.1
-
Fix Version/s: EE-4.2.0.GA
-
Component/s: JavaScript Client, Push Library
-
Labels:None
-
Environment:ICEpush JavaScript Bridge, ICEpush Core
-
Assignee Priority:P1
Description
Instead of lazily adding the ice.notifyBack to the listen.icepush requests upon registering for cloud push and resulting in the eventual server-side NotifyBackURI representation, we should introduce new .icepush requests specifically for this:
1. add-notify-back-uri.icepush
2. has-notify-back-uri.icepush
3. remove-notify-back-uri.icepush
All these requests should be kept quite simple. The add request should at a minimum include the browserID and notifyBackURI as only the client-side is able to obtain the notifyBackURI. The response to the add request can likely just be a 200 OK or 204 No Content status message. The has request should at a minimum include the browserID. This request can be used by the cloud/mobile component to check if its browserID already has a notifyBackURI associated with it. The response to the has request can likely just be a 200 OK or 204 No Content status message indicating its browserID has a notifyBackURI associated with it, or it can likely just be a 404 Not Found status message indicating its browserID has no notifyBackURI associated with it.
For this both the client-side and server-side need to include support for these new .icepush requests.
1. add-notify-back-uri.icepush
2. has-notify-back-uri.icepush
3. remove-notify-back-uri.icepush
All these requests should be kept quite simple. The add request should at a minimum include the browserID and notifyBackURI as only the client-side is able to obtain the notifyBackURI. The response to the add request can likely just be a 200 OK or 204 No Content status message. The has request should at a minimum include the browserID. This request can be used by the cloud/mobile component to check if its browserID already has a notifyBackURI associated with it. The response to the has request can likely just be a 200 OK or 204 No Content status message indicating its browserID has a notifyBackURI associated with it, or it can likely just be a 404 Not Found status message indicating its browserID has no notifyBackURI associated with it.
For this both the client-side and server-side need to include support for these new .icepush requests.
Activity
Jack Van Ooststroom
created issue -
Jack Van Ooststroom
made changes -
Field | Original Value | New Value |
---|---|---|
Assignee | Jack Van Ooststroom [ jack.van.ooststroom ] |
Jack Van Ooststroom
made changes -
Fix Version/s | EE-4.1.0.GA [ 12172 ] |
Jack Van Ooststroom
made changes -
Attachment | PUSH-390.patch [ 22123 ] |
Jack Van Ooststroom
made changes -
Assignee | Jack Van Ooststroom [ jack.van.ooststroom ] | Mircea Toma [ mircea.toma ] |
Ken Fyten
made changes -
Assignee Priority | P1 [ 10010 ] |
Mircea Toma
made changes -
Attachment | PUSH-390.client-side.patch [ 22124 ] |
Mircea Toma
made changes -
Assignee | Mircea Toma [ mircea.toma ] | Jack Van Ooststroom [ jack.van.ooststroom ] |
Repository | Revision | Date | User | Message |
ICEsoft Public SVN Repository | #48626 | Wed Apr 13 16:35:27 MDT 2016 | jack.van.ooststroom | Fixed JIRA |
Files Changed | ||||
MODIFY
/icefaces4/trunk/icefaces/core/src/main/java/org/icefaces/impl/push/servlet/ICEpushResourceHandler.java
MODIFY /icefaces4/trunk/icefaces/core/src/main/java/org/icefaces/impl/event/BridgeSetup.java |
Repository | Revision | Date | User | Message |
ICEsoft Public SVN Repository | #48629 | Thu Apr 14 13:31:10 MDT 2016 | mircea.toma | |
Files Changed | ||||
ADD
/icefaces4/trunk/icefaces/core/src/main/resources/META-INF/resources/add-notify-back-uri.icepush.txt
ADD /icefaces4/trunk/icefaces/core/src/main/resources/META-INF/resources/has-notify-back-uri.icepush.txt ADD /icefaces4/trunk/icefaces/core/src/main/resources/META-INF/resources/remove-notify-back-uri.icepush.txt |
Jack Van Ooststroom
made changes -
Status | Open [ 1 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] |
Ken Fyten
made changes -
Fix Version/s | EE-4.1.0.BETA [ 13073 ] |
Ken Fyten
made changes -
Fix Version/s | EE-4.1.1.BETA [ 13077 ] | |
Fix Version/s | EE-4.1.0.GA [ 12172 ] | |
Fix Version/s | EE-4.1.0.RC1 [ 13073 ] |
Ken Fyten
made changes -
Fix Version/s | EE-4.2.0.GA [ 13074 ] | |
Fix Version/s | EE-4.1.1.BETA [ 13077 ] |
Repository | Revision | Date | User | Message |
ICEsoft Public SVN Repository | #50746 | Mon Feb 27 09:46:53 MST 2017 | jack.van.ooststroom | Reverted |
Files Changed | ||||
MODIFY
/icefaces4/trunk/icefaces/core/src/main/java/org/icefaces/impl/push/servlet/ICEpushResourceHandler.java
MODIFY /icefaces4/trunk/icefaces/core/src/main/java/org/icefaces/impl/event/BridgeSetup.java |
Repository | Revision | Date | User | Message |
ICEsoft Public SVN Repository | #50761 | Mon Feb 27 16:30:58 MST 2017 | jack.van.ooststroom | Reverted |
Files Changed | ||||
DEL
/icefaces4/trunk/icefaces/core/src/main/resources/META-INF/resources/add-notify-back-uri.icepush.txt
DEL /icefaces4/trunk/icefaces/core/src/main/resources/META-INF/resources/has-notify-back-uri.icepush.txt DEL /icefaces4/trunk/icefaces/core/src/main/resources/META-INF/resources/remove-notify-back-uri.icepush.txt |
Attached client side changes. I also modified the response of HasNotifyBackURI servlet to always respond with a OK 200, the response body will contain the 'true' or 'false' string depending what the result of the test it is. I believe we do not need to carry procedure invocation concepts into the HTTP realm. Also code handling on the client side is much simpler and straight forward.