Thanks Dilip ,
Are you sure that you want to reverse the priorities on
the client vs the server? I cannot find any reference for
this. I am wondering if maybe the priority indicates the
order for soap message send, and the reverse order is
used for soap message receipt? That would be more
consistent.
I guess I should test it. Would love a MSDN reference for
this.
I am confused about what group is for too. I see the
reference :
The three relative priority groups for SOAP extensions
are: SOAP extensions configured using an attribute and
SOAP extensions specified in the configuration file with
a group setting of 0 or 1. SOAP extensions configured
using an attribute are members of the medium group. SOAP
extensions configured using a configuration file with a
group setting of 0 have the highest relative priority.
Those with a group setting of 1 have the lowest relative
priority.
But not sure what this means exactly.
Jon Paugh
-----Original Message-----
Hello Jon,
Whatever order you choose at the client the reverse
order needs to be appliedon the server side.
Client if the priorities are like this Compression 0 -
Encryption - 1 meansits going to compress first and encrypt after
Server needs to have the priorities like this
Compression 1 - Encryption- 0 means its going to decrypt first and uncompress later
HTH
Regards,
Dilip Krishnan
MCAD, MCSD.net
dkrishnan at geniant dot com
http://www.geniant.com
Hi,
If I have two soap extensions, one to encrypt data,
and the other to compress data, which should have higher priority on
the client, and on the server?
The information I have indicates that priority
determines the order in which soap extensions are applied. But I would think
they would be applied in reverse order for serialization vs.
deserialization too (as this case would require)?
Thanks,
Jon Paugh
.