Is he writing a web service?  Use WSE 3.0 and have him send it as an MTOM
attachment, which he can stream.  On your end hook into the chain and save
it as you are receiving it.

Otherwise have him write a stateful service and request it in chunks.

-----Original Message-----
From: Discussion of advanced .NET topics.
[mailto:[EMAIL PROTECTED] On Behalf Of Franklin Gray
Sent: Friday, August 17, 2007 12:40 PM
To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM
Subject: [ADVANCED-DOTNET] http request streaming

I'm new to this company and I've been placed on a project with a java
developer who wants to send me (a windows VB.net developer) a file from
unix (java) to windows but he doesn't want to use FTP.  He asked me to
write a web service.  So I did but he didn't like that he has to call it
via a soap format.  He now says what he wants is something that will
receive a streaming http request (sending me an xml file) that I would
receive the stream and save the bytes into a file as they are sent (so
that I will never had the entire file in memory).

1 solution that I can think of to do this is to open a data socket and
listen to a port and then send back messages.  I've used sockets in my
program to FTP files via the FTP protocol but not sure how much this is
different.

Another solution that I can think of is to create a web service with a
start, a write (excepting 512 bytes at a time), an End to receive the file
and a start, read, end to send the file back to him.  This isn't that hard
but he hates the idea.  He doesn't like that he has to write soap
formatted calls (to call my web service from java).

Is there another way that I can write an http streaming request listener?

In a tight spot...please help,
Franklin

===================================
This list is hosted by DevelopMentorĀ®  http://www.develop.com

View archives and manage your subscription(s) at http://discuss.develop.com

===================================
This list is hosted by DevelopMentorĀ®  http://www.develop.com

View archives and manage your subscription(s) at http://discuss.develop.com

Reply via email to