Our product system consists of an IIS 6.0 server, behind which is a Java SOA server, behind which are both Oracle database servers.
For various reasons, we need a Windows service running on a Java SOA server that stores opaque drops associated with a GUID. Here is a simplified version of the interface:
interface IBlobService
{
void PutBlob(Guid key, byte[] data);
byte[] GetBlob(Guid key);
}
The primary user of IBlobService is the web interface running on the IIS server. We could use remote WCF or .NET through a special port for communication between servers. However, our application is subject to strict accreditation requirements. We would rather use a well-known port for communication rather than a user port.
We cannot use named pipes because we need to communicate between servers. We examined the use of MSMQ as it uses a well-known port, but MSMQ limits the message size to 4 MB. We need to transfer much more - up to 60 MB, at least.
What other features (if any) do .NET expose that will allow communication between servers over a known port?
source
share