Re: RCVJRNE/exitpgm vs. Mimix

I don't think the MQ overhead should be anything to worry about (unless
the OP is anticipating 100s of updates per second, or more, in which
case an Connect, Open, Put, Put , Put,.. , Close, Disconnect structure
would be more appropriate).

Splitting the processing into stages would be a good idea from a
testing point of view - it should makes things much simpler - however,
the only thing to watch for when using DTAQs is that you can't directly
see the content of the messages on them (you have to write / acquire a
utility program to do this), whereas you can do this easily with MQ.

.

Relevant Pages

  • Re: Installed update - Update history differ
    ... Don't worry about that one ... Windows Vista Home Basic 32 bit SP1 ... Download, install and run. ... When I look in Installed updates, many of the Updates, ...
    (microsoft.public.windowsupdate)
  • Re: Redirect stdout and stderr preserving the original order
    ... My worry would be that I don't have very high confidence ... that it'll respond immediately to updates in the files -- meaning ...
    (comp.unix.shell)
  • Re: Help and Support Center
    ... Yes, don't worry, it's very minor. ... Lately (since july+aug updates) the Did You Know issue has been a lot ... now it's just a single "Set Search Options" headline ... the "headlines" are all pretty mundane! ...
    (microsoft.public.windowsxp.general)
  • Re: System File Check
    ... The people who make the updates are the same people who made the original ... You know something, you worry too much. ... > service packs already ...
    (microsoft.public.windowsxp.perform_maintain)
  • Re: Business Objects and Async Message Based Systems
    ... > for validation / updates in a single object is that it lightens the load ... > for the UI deveoper not to have to worry about such issues. ... > sizeTextBox and an IsValid property to the submitButton. ...
    (microsoft.public.dotnet.languages.csharp)