[wsf-c-dev] [jira] Commented: (WSFC-250) Implement WS-RM Mercury in
C
damitha kumarage (JIRA)
jira at wso2.org
Sun May 4 23:28:17 PDT 2008
[ https://wso2.org/jira/browse/WSFC-250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16486#action_16486 ]
damitha kumarage commented on WSFC-250:
---------------------------------------
I closely looked at the Mercury java architecture documents/diagrams and implementation. It seems to me that the design using the state machine is much cleaner and abstract/hide much of the complexities that is aparent in the Sandesh2 architecture. Also when looking at the implementation I can see that we can re-use most of the existing Sandesha2/C code in Mercury/C, for example code regarding RM message elements could be used as it is.
The main change in architecture is that Sandesha2 architecture is based around message processors for each kind of messages and Mercury instead completely get rid of message processor concept and adapt with the state changes of the state machine.
Because of the possiblity of code reuse, I can see that Mercury/C could be implemented in a relatively shorter duration than I though initially before analysing architecture/code.
> Implement WS-RM Mercury in C
> ----------------------------
>
> Key: WSFC-250
> URL: https://wso2.org/jira/browse/WSFC-250
> Project: WSO2 WSF/C
> Issue Type: Task
> Components: Apache Sandesha/C (RM)
> Reporter: damitha kumarage
> Original Estimate: 8 weeks
> Remaining Estimate: 8 weeks
>
> WS-RM new model in Mercury can be implemented in C.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://wso2.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the Wsf-c-dev
mailing list