DIME Attachments using WSE2 SP3 on .net 2.0

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Shane Warren - 09 Nov 2005 18:13 GMT

Ok, first I was dismayed that microsoft decided to do away with DIME
attachments in WSE3 because I have a application that relies on that
feature. Now after upgrading to 2005 and getting the 2.0 framework on my
dev machine my old application (still using WSE2 SP3) that worked fine using
streaming DIME now randomly blows up (somewhere deep in the streaming code,
something along the lines about my host closing the connection), and like
its strange it works 1 out of 10 times, then randomly throws that weird
exception every once in a while. So now its 2 strikes, no streaming dime in
WSE3 and (and this is a HUGE and) WSE2 stuff doesn't work right when you
have the .net framework 2.0 installed.

So I've read somewhere that WSE2 will be updated to work with the 2.0
framework, is this really true, I surely hope so or anyone who used DIME
attachements in WSE2 will be in the same sinking boat as me. And I know
MTOM is out there but MTOM totally doesn't fit my needs, I am streaming
large files to a non windows server that supports streaming DIME and doesn't
support streaming MTOM, why would I want streaming MTOM anyway it appears to
only support sending stuff over the wire using base64, didn't we take a step
backwards here?

Reply to this Message

William Stacey [MVP] - 09 Nov 2005 21:11 GMT

I agree. TMK, you can stream the send in binary. However the receiver has
to read the whole message, so this does not work real well for large files.
Not sure this is an option for you, but .net remoting can stream files
pretty well. I have beat ftp and webrequest speed in my dev tests and they
stream/chunk both ways.

Signature

William Stacey [MVP]

> Ok, first I was dismayed that microsoft decided to do away with DIME
> attachments in WSE3 because I have a application that relies on that
[quoted text clipped - 15 lines]
> appears to only support sending stuff over the wire using base64, didn't
> we take a step backwards here?

Reply to this Message

Shane Warren - 09 Nov 2005 21:59 GMT

As I said the other side of this soap conversation is not a windows box, it
cannot use remoting.

My point of my first post was: Why did Microsoft break WSE2 when running on
the 2.0 .net framework?

The scenario is like this: lets say people have apps out in the field using
WSE2 and now a client sees the 2.0 framework is available on windows update
(it isn't but I'm sure in time it will be), grabs it and now all that stuff
that used WSE2 will start randomly crashing when soap calls are made.

Why is it that API writers haven't learned to NOT change the behavior of
existing calls, how many times has this bitten developers? If a function is
wrong, don't change it in a way that breaks existing calls, make a new
fuction. You would think in the shining achievement that is the .net 2.0
framework they would have thought this through and not broken existing
API's, I guess history really does repeat itself.

What I really want to know is this: Will WSE2 have a new service pack (SP4?)
that fixes this problem or are all those people who wrote stuff using WSE2
now left out in the rain?

>I agree. TMK, you can stream the send in binary. However the receiver has
>to read the whole message, so this does not work real well for large files.
[quoted text clipped - 21 lines]
>> appears to only support sending stuff over the wire using base64, didn't
>> we take a step backwards here?

Reply to this Message

David C - 16 Nov 2005 00:12 GMT

Shane, if this is true then this is really, really critical. We are currently
developing an app that will be distributed to thousands of sites and uses
DIME and WSE 2 SP3. Is someone from Microsoft prepared to make a comment here?

DC

> As I said the other side of this soap conversation is not a windows box, it
> cannot use remoting.
[quoted text clipped - 43 lines]
> >> appears to only support sending stuff over the wire using base64, didn't
> >> we take a step backwards here?

Reply to this Message

DIME Attachments using WSE2 SP3 on .net 2.0

Free Magazines