If you are a web services developer and you build a new SOA system, you probably choose HTTP as a transport. However, sometimes you should support legacy systems that use other protocols for information exchange, for example, FTP. There are several technical nuances to be addressed in this case:
- If client sends data over HTTP, you may analyze it and reply with an error code if it’s incorrect. If the client uploads data by FTP, how will you notify that client that you can’t accept it?
- The incoming directory for clients’ uploads may contain bad data – you should add a verification code to file processing job.
Both problems can be solved using SOA Expressway – the better, more flexible implementation of the XML Gateway pattern.
Read more about this in Anton’s post: