Hi Hung,
Good to see that you did not give up on this one.
I started reviewing on Friday but got interrupted by som other stuf.
Will continue to review today.
/AndersBj
From: Hung Nguyen [mailto:xhun...@users.sf.net]
Sent: den 20 april 2015 07:36
To: [opensaf:tickets]
Subject: [opensaf:tickets] #969 IMM: remove all use of SaNameT from IMM server
side and messages
* status: assigned --> review
________________________________
[tickets:#969]<http://sourceforge.net/p/opensaf/tickets/969> IMM: remove all
use of SaNameT from IMM server side and messages
Status: review
Milestone: 4.7-Tentative
Created: Thu Jul 24, 2014 01:59 PM UTC by Anders Bjornerstedt
Last Updated: Thu Mar 26, 2015 12:30 PM UTC
Owner: Hung Nguyen
All usage of SaNameT should be purged from the IMM server side code.
For message types we need backwards compatibility.
But new versions should be defined for all messages that currently use
SaNameT and the new message version should be used in the release where this
ticket is fixed, subject to the protocol46Allowed bit in noStdFlags.
The message packing unpacking code should on the server side transform
to the new message type as part of unpacking.
On the IMMA client side, usage of SaNameT should be confined to only the
very top layer of the old API, when enhancement #643 is fixed.
http://sourceforge.net/p/opensaf/tickets/643/<http://sourceforge.net/p/opensaf/tickets/643>
________________________________
Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/opensaf/tickets/969/<https://sourceforge.net/p/opensaf/tickets/969>
To unsubscribe from further messages, please visit
https://sourceforge.net/auth/subscriptions/<https://sourceforge.net/auth/subscriptions>
---
** [tickets:#969] IMM: remove all use of SaNameT from IMM server side and
messages**
**Status:** review
**Milestone:** 4.7-Tentative
**Created:** Thu Jul 24, 2014 01:59 PM UTC by Anders Bjornerstedt
**Last Updated:** Mon Apr 20, 2015 05:36 AM UTC
**Owner:** Hung Nguyen
All usage of SaNameT should be purged from the IMM server side code.
For message types we need backwards compatibility.
But new versions should be defined for all messages that currently use
SaNameT and the new message version should be used in the release where this
ticket is fixed, subject to the protocol46Allowed bit in noStdFlags.
The message packing unpacking code should on the server side transform
to the new message type as part of unpacking.
On the IMMA client side, usage of SaNameT should be confined to only the
very top layer of the old API, when enhancement #643 is fixed.
http://sourceforge.net/p/opensaf/tickets/643/
---
Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is
subscribed to http://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
http://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
_______________________________________________
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
