This week's book giveaway is in the JavaScript forum.
We're giving away four copies of Cross-Platform Desktop Applications: Using Node, Electron, and NW.js and have Paul Jensen on-line!
See this thread for details.
Win a copy of Cross-Platform Desktop Applications: Using Node, Electron, and NW.js this week in the JavaScript forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

SOAP over FTP  RSS feed

 
kumar puppala
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I am new to this discussion group.
Currently, our application is using SOAP over HTTP to retreive documents(PDF, TIF, XLS) in the form of attachments. Everything seems to be working fine untill we run into issues with the size of the data being pulled by the Client. If the size exceeds a certain limit, they run out of memory to load that image. One of the suggestions given here was to chuck the data being retrieved and save it to the disk and load it. But this is very inefficient as it would involve several SOAP messages and the overhead of combining all these chucks of data. Is there any alternative to this? Can we use FTP as the transport layer instead of HTTP for retrieving these attachments? Any input is appreciated.
 
Lasse Koskela
author
Sheriff
Posts: 11962
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Running out of memory isn't a problem with the protocol being used (HTTP) so I doubt that using FTP would help much in that regard. What kind of sizes are we talking about here? Would it be possible to simply increase the maximum memory available to the JVM?
 
kumar puppala
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The reason I thought FTP would solve the problem is because we can save the attachment onto the disk and load it from the disk. That way we dont need to load it directly from the memory. We are looking at files whose sizes maybe about 20MB.
 
Lasse Koskela
author
Sheriff
Posts: 11962
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The problem is still there because you need to read the documents into memory at some point -- that's just the way your SOAP engine works. The SOAP over FTP solution would however enable "queueing" functionality, which would make it possible to "throttle" the processing of those SOAP messages so that you'll only have one or two of these 20-megabyte messages in memory at any time.
Are you aware of any available SOAP implementations supporting FTP as the transport, by the way?
 
kumar puppala
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks Lasse for your response. I am not aware of any implementations of SOAP over FTP. I am still researching this. Do you know any such implementations and if so, how reliable are those implementations?
 
Lasse Koskela
author
Sheriff
Posts: 11962
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by kumar puppala:
Do you know any such implementations and if so, how reliable are those implementations?
I'm not aware of such beasts either. Sorry.
I was actually playing with the thought of writing some code utilizing FTP, and a directory-polling web services client; kind of like a "file system based web services proxy"...
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!