until approx. 1-2 years ago, I have seen that the synchronous MDN was preferred over asynchronous MDNs, mainly because it is easier to setup and the response was quicker, since it is all handled within one connection.
So if you were only sending data to a partner, you wouldn´t even have to configure anything on the Inbound side (like opening the firewall for inbound traffic or providing an IP-address/URL to your partners).
In the last 1-2 years I have seen a lot of companies requesting to use asynchronous MDN which I assume was mainly causes by performance issues...so that the session had not to be kept open until the MDN was created on the receiving system..
So with async MDNs... the sending-session is immediately closed once the file is transmitted and the receiver can send back the MDN whenever he likes or whenever he has the possibility/bandwidth to do so.
Also he has better options to check the file before he sends back the MDN.
(however, I have seen that most systems anyway send back the MDN within the next second, even if its asynchronous)
thanks for your response ,sorry for the delay response
in your previous post you have mentioned (In the last 1-2 years I have seen a lot of companies requesting to use asynchronous MDN which I assume was mainly causes by performance issues)
could you please elaborate performance issues
how can we found which seeburger version we are using (i am new to seeburger AS2)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.