WSE / DIME File Transfer Performance

[Joseph Geretz]

I'm working on an file transfer gateway using WSE with DIME for file
attachments. Our goal is to replace our direct file repository access (via
windows network folder sharre) with the Web Service gateway for security
purposes.

As it stands now, all workstations have direct read-write access to the file
repository share. The Web Service gateway will secure this for us. While the
web service gateway is more secure, it doesn't perform anywhere near up to
the performance of a direct file copy. I'm working with a 27 MB file in my
test environment; the client and the web service are on the same
workstation.

Using direct file access, I can copy this 27 MB file in under 2 seconds.
Using the web service, it take between 5 and 6 seconds to transfer the same
file. We understand that we might have to trade a bit of speed for the
increased security, however a 400% increase is really more of a hit than
we'd been anticipating. Is there any way that I can tune performance to
optimize WSE / DIME for large file attachments?

Thanks for your help!

- Joe Geretz -

[Jim Rand]

Hi Joseph,

Do a Google search on "084SharpZipLib". Check out
084SharpZipLib_SourceSamples.zip and the DIME example.

Jim

"Joseph Geretz" <jg*****@nospam.com> wrote in message
news:Od**************@TK2MSFTNGP12.phx.gbl...

I'm working on an file transfer gateway using WSE with DIME for file
attachments. Our goal is to replace our direct file repository access (via
windows network folder sharre) with the Web Service gateway for security
purposes.

As it stands now, all workstations have direct read-write access to the file repository share. The Web Service gateway will secure this for us. While the web service gateway is more secure, it doesn't perform anywhere near up to
the performance of a direct file copy. I'm working with a 27 MB file in my
test environment; the client and the web service are on the same
workstation.

Using direct file access, I can copy this 27 MB file in under 2 seconds.
Using the web service, it take between 5 and 6 seconds to transfer the same file. We understand that we might have to trade a bit of speed for the
increased security, however a 400% increase is really more of a hit than
we'd been anticipating. Is there any way that I can tune performance to
optimize WSE / DIME for large file attachments?

Thanks for your help!

- Joe Geretz -

[Joseph Geretz]

Hi Jim,

What does this do, Zips the file before sending it across the wire? Most of
our files are compressed to begin with, so this wouldn't buy us anything in
most cases.

Thanks,

- Joe Geretz -

"Jim Rand" <ji*****@ix.netcom.com> wrote in message
news:up**************@TK2MSFTNGP15.phx.gbl...

Hi Joseph,

Do a Google search on "084SharpZipLib". Check out
084SharpZipLib_SourceSamples.zip and the DIME example.

Jim

"Joseph Geretz" <jg*****@nospam.com> wrote in message
news:Od**************@TK2MSFTNGP12.phx.gbl...

I'm working on an file transfer gateway using WSE with DIME for file
attachments. Our goal is to replace our direct file repository access
(via
windows network folder sharre) with the Web Service gateway for security
purposes.

As it stands now, all workstations have direct read-write access to the

file

repository share. The Web Service gateway will secure this for us. While

the

web service gateway is more secure, it doesn't perform anywhere near up
to
the performance of a direct file copy. I'm working with a 27 MB file in
my
test environment; the client and the web service are on the same
workstation.

Using direct file access, I can copy this 27 MB file in under 2 seconds.
Using the web service, it take between 5 and 6 seconds to transfer the

same

file. We understand that we might have to trade a bit of speed for the
increased security, however a 400% increase is really more of a hit than
we'd been anticipating. Is there any way that I can tune performance to
optimize WSE / DIME for large file attachments?

Thanks for your help!

- Joe Geretz -

[Jim Rand]

Oh well. :-(

"Joseph Geretz" <jg*****@nospam.com> wrote in message
news:ev**************@TK2MSFTNGP09.phx.gbl...

Hi Jim,

What does this do, Zips the file before sending it across the wire? Most of our files are compressed to begin with, so this wouldn't buy us anything in most cases.

Thanks,

- Joe Geretz -

"Jim Rand" <ji*****@ix.netcom.com> wrote in message
news:up**************@TK2MSFTNGP15.phx.gbl...

Hi Joseph,

Do a Google search on "084SharpZipLib". Check out
084SharpZipLib_SourceSamples.zip and the DIME example.

Jim

"Joseph Geretz" <jg*****@nospam.com> wrote in message
news:Od**************@TK2MSFTNGP12.phx.gbl...

I'm working on an file transfer gateway using WSE with DIME for file
attachments. Our goal is to replace our direct file repository access
(via
windows network folder sharre) with the Web Service gateway for security purposes.

As it stands now, all workstations have direct read-write access to the

file

repository share. The Web Service gateway will secure this for us. While

the

web service gateway is more secure, it doesn't perform anywhere near up
to
the performance of a direct file copy. I'm working with a 27 MB file in
my
test environment; the client and the web service are on the same
workstation.

Using direct file access, I can copy this 27 MB file in under 2

seconds. Using the web service, it take between 5 and 6 seconds to transfer the

same

file. We understand that we might have to trade a bit of speed for the
increased security, however a 400% increase is really more of a hit than we'd been anticipating. Is there any way that I can tune performance to
optimize WSE / DIME for large file attachments?

Thanks for your help!

- Joe Geretz -