Details
New Feature
Major
Description
Add the ability to "publish now" to the MessageServiceClient. The current publish(...) methods don't actually publish the message directly. Instead the message is put in a MessagePipeline in order to give the MessageServiceClient a chance to gather multiple message before publishing a big concatenated message. The introduction of publishNow(...) methods should give us the ability to directly publish a message giving the ability to act directly on failure as well.
Activity
| Repository | Revision | Date | User | Message |
| ICEsoft Public SVN Repository | #18651 | Wed Mar 25 13:41:43 MDT 2009 | jack.van.ooststroom | Fixed JIRA |
| Files Changed | ||||
MODIFY
/icefaces/trunk/icefaces/core/src/com/icesoft/faces/webapp/http/servlet/MainServlet.java
MODIFY
/icefaces/trunk/icefaces/core/src/com/icesoft/net/messaging/http/HttpAdapter.java
MODIFY
/icefaces/trunk/icefaces/core/src/com/icesoft/net/messaging/MessageServiceClient.java
|
| Field | Original Value | New Value |
|---|---|---|
| Assignee | Jack Van Ooststroom [ jack.van.ooststroom ] |
| Salesforce Case | [] | |
| Fix Version/s | 1.8 [ 10161 ] |
| Status | Open [ 1 ] | In Progress [ 3 ] |
I added the publishNow(...) method equivalents of the publish(...) methods. Note that the publishNow(...) methods might throw a MessageServiceException. The MainServlet now uses the publishNow(...) method to potentially fail quickly in case the Push Server is not there. Marking this one as FIXED.
Show
Jack Van Ooststroom
added a comment - I added the publishNow(...) method equivalents of the publish(...) methods. Note that the publishNow(...) methods might throw a MessageServiceException. The MainServlet now uses the publishNow(...) method to potentially fail quickly in case the Push Server is not there. Marking this one as FIXED.
| Status | In Progress [ 3 ] | Resolved [ 5 ] |
| Resolution | Fixed [ 1 ] |
| Status | Resolved [ 5 ] | Closed [ 6 ] |
| Assignee | Jack van Ooststroom [ jack.van.ooststroom ] |
Changed Fix Version(s) to 1.8.0