[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [no subject]
=20 Regarding UseNotify, it would be nice if a producer could choose to require UseNotify. I can think of two ways this could be done: =20 1) Add a NotifyRequired xs:boolean resource prop to the NotificationProducer portType 2) Add a notifyRequired xs:boolean attribute to the wstop:Topic element The latter would allow the flag to be specified per topic but would be more difficult for clients to ascertain. In either case, I think a NotifyRequiredFault would need to be added to the subscribe operation. =20 Ian ________________________________ From: Sedukhin, Igor S [mailto:Igor.Sedukhin@ca.com]=20 Sent: Thursday, March 24, 2005 11:48 AM To: wsdm@lists.oasis-open.org Cc: wsn@lists.oasis-open.org Subject: [wsdm] Notify wrapped vs Soap body =09 =09 So the wsnt:Notify/wsnt:NotificationMessage/wsnt:Messaage is xs:anyType while soap:Envelope/soap:Body is a container of xs:any. This creates a serialization hell since any given object needs to be serialized sligtly differently, in principle. More over objects that serialze directly in value could not be sent unwrapped, but could be sent Notify wrapped. Since indication of UseNotify is at the subscriber's will, it may result in a bunch of interoperability problems. -- Igor Sedukhin .. (igor.sedukhin@ca.com <mailto:igor.sedukhin@ca.com> ) -- (631) 342-4325 .. 1 CA Plaza, Islandia, NY 11749=20 ------_=_NextPart_001_01C53093.19FAB9A5 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD><TITLE>Notify wrapped vs Soap body</TITLE> <META http-equiv=3DContent-Type content=3D"text/html; = charset=3Dus-ascii"> <META content=3D"MSHTML 6.00.2900.2604" name=3DGENERATOR></HEAD> <BODY> <DIV dir=3Dltr align=3Dleft><SPAN class=3D042365216-24032005><FONT = face=3DArial=20 color=3D#0000ff size=3D2>From my experience, xs:anys pretty much = always cause=20 serialization hell. </FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D042365216-24032005><FONT = face=3DArial=20 color=3D#0000ff size=3D2></FONT></SPAN> </DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D042365216-24032005><FONT = face=3DArial=20 color=3D#0000ff size=3D2>Regarding UseNotify, it would be nice if a = producer could=20 choose to require UseNotify. I can think of two ways this could be=20 done:</FONT></SPAN></DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D042365216-24032005><FONT = face=3DArial=20 color=3D#0000ff size=3D2></FONT></SPAN> </DIV> <DIV dir=3Dltr align=3Dleft><SPAN class=3D042365216-24032005><FONT = face=3DArial=20 color=3D#0000ff size=3D2>1) Add a NotifyRequired xs:boolean = resource prop to=20 the NotificationProducer portType</FONT></SPAN></DIV> <DIV><SPAN class=3D042365216-24032005><FONT face=3DArial color=3D#0000ff = size=3D2>2) Add=20 a notifyRequired xs:boolean attribute to the wstop:Topic=20 element</FONT></SPAN></DIV><FONT face=3DArial color=3D#0000ff = size=3D2></FONT><FONT=20 face=3DArial color=3D#0000ff size=3D2></FONT> <DIV><BR><SPAN class=3D042365216-24032005><FONT face=3DArial = color=3D#0000ff=20 size=3D2>The latter would allow the flag to be specified per topic but = would be=20 more difficult for clients to ascertain. In either case, I think a=20 NotifyRequiredFault would need to be added to the subscribe=20 operation.</FONT></SPAN></DIV> <DIV><SPAN class=3D042365216-24032005><FONT face=3DArial color=3D#0000ff = size=3D2></FONT></SPAN> </DIV> <DIV><SPAN class=3D042365216-24032005><FONT face=3DArial color=3D#0000ff = size=3D2>Ian</FONT></SPAN></DIV> <BLOCKQUOTE dir=3Dltr=20 style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px = solid; MARGIN-RIGHT: 0px"> <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft> <HR tabIndex=3D-1> <FONT face=3DTahoma size=3D2><B>From:</B> Sedukhin, Igor S=20 [mailto:Igor.Sedukhin@ca.com] <BR><B>Sent:</B> Thursday, March 24, = 2005 11:48=20 AM<BR><B>To:</B> wsdm@lists.oasis-open.org<BR><B>Cc:</B>=20 wsn@lists.oasis-open.org<BR><B>Subject:</B> [wsdm] Notify wrapped vs = Soap=20 body<BR></FONT><BR></DIV> <DIV></DIV><!-- Converted from text/rtf format --> <P><FONT face=3DArial size=3D2>So the=20 wsnt:Notify/wsnt:NotificationMessage/wsnt:Messaage is xs:anyType while = soap:Envelope/soap:Body is a container of xs:any. This creates a = serialization=20 hell since any given object needs to be serialized sligtly = differently, in=20 principle. More over objects that serialze directly in value could not = be sent=20 unwrapped, but could be sent Notify wrapped. Since indication of = UseNotify is=20 at the subscriber's will, it may result in a bunch of interoperability = problems.</FONT></P> <P><SPAN lang=3Dde><FONT face=3D"Times New Roman" color=3D#800080=20 size=3D2>--</FONT><FONT face=3DArial size=3D2><B> </B></FONT><B><FONT = face=3DArial=20 color=3D#000080 size=3D2>Igor Sedukhin</FONT></B><FONT face=3DArial = size=3D2></FONT>=20 <FONT face=3D"Times New Roman" color=3D#c0c0c0 size=3D2>..</FONT><FONT = face=3DArial=20 size=3D2> </FONT><FONT face=3DArial color=3D#800080 = size=3D2>(</FONT></SPAN><A=20 href=3D"mailto:igor.sedukhin@ca.com";><SPAN lang=3Dde><U><FONT = face=3DArial=20 color=3D#0000ff = size=3D2>igor.sedukhin@ca.com</FONT></U></SPAN></A><SPAN=20 lang=3Dde><FONT face=3DArial color=3D#800080 = size=3D2>)</FONT><BR><FONT=20 face=3D"Times New Roman" color=3D#800080 size=3D2>--</FONT><FONT = face=3DArial=20 size=3D2></FONT><B> <FONT face=3DArial color=3D#808080 size=3D2>(631)=20 342-4325</FONT></B><FONT face=3DArial size=3D2></FONT> <FONT=20 face=3D"Times New Roman" color=3D#c0c0c0 size=3D2>..</FONT><FONT = face=3DArial=20 size=3D2></FONT></SPAN><SPAN lang=3Den-us> <FONT face=3DArial = color=3D#008080 size=3D2>1=20 CA Plaza, Islandia, NY 11749</FONT></SPAN> = </P></BLOCKQUOTE></BODY></HTML> ------_=_NextPart_001_01C53093.19FAB9A5--
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]