Sounds like an agitator to me. SOAP and web services? <sarcasm>I think the two have been used together occasionally</sarcasm>.
If you were going the listening to a port route, you'll have to create your own server, implementing HTTP if that's the protocol you want to use-- not very productive, IMHO. The benefit of the web service method is you're building upon IIS and it can be managed by existing admins through their existing interfaces. Introducing a new web server means it cannot be managed by existing policies or existing interfaces and will require admins to learn something new--expect pushback on that. While there's a SOAP overhead to web services, you're essentially free to format the payload how ever you see fit. You can send that as an encrypted/compressed blob and only use a minimal amount of SOAP. I fail to see how he could have issue with "SOAP", other than he doesn't understand it. If it were me, I would just point him to the web service and say "use that". After all, it sounds like he's got everything he needs on the server side. On Fri, 17 Aug 2007 12:39:37 -0400, Franklin Gray <[EMAIL PROTECTED]> wrote: >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? =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
