Alex wrote: > I have an application that connects over a stateful protocol to an outside > vendor. As a matter of course we sleep for 30 seconds until we reconnect, > just so as to allow the remote side to reset and line up the transactions > that need to be replayed. > > Perhaps not an elegant way of solving problems where the remote side is a > little slow, but it's simple and acceptable to us.
That sounds like an implementation issue for the application. From the SMF view point it is better to have the application startup so that SMF sees it is running and have the application do the wait for 30seconds before doing what it does. -- Darren J Moffat
