Hi,
I'm new to .NET remoting and there's something I'm having real trouble with.
Basically, I'd like to create a component that can act as a server and as a
client (can send messages and receive them in asynchronous mode).
Here's the situation just so you guys understand why I'm doing this (and
maybe so that you can provide me with other options):
I have an application that needs to save data to a remote database. The
DBAs don't allow direct modifications or insertions into the database for
security and other reasons. So, they built what we call here an INSERTION
SERVICE (IS). The application that wants to save to the db has to create an
XML file with the details of the changes and drop it on an FTP site for
processing. Problem is that files can be rejected for many reasons so we
would like to inform the user whether his changes have been done or not.
Since this is a very busy database, the changes are not necessarily done
immediately, the files are put in a priority queue.
So basically, once the changes have been made or not, we need to inform the
user in the App. We thought about building some kind of proxy that resides
between the application and the IS. The application would register itself to
the proxy everytime it sends a new file to the IS. Once the file has been
processed, the IS could send a message to the proxy that would dispatch it to
the App. So, the App would need to act as a client for the original
registration to the proxy and as a server for the reception of the final
message (vice-versa for the proxy).
There might be a better way of doing this but I don't see it. With basic
..NET Remoting, I could do it by having the client wait for the IS to answer
and then send that answer to the client but since I have no idea how long
that could take, It's not a good option.
Thanks a lot in advance for all your help,
Skip.