Messaging?

[persian_83]

Should we always use messaging in our *****peer ( or any other non browswer remote program ) programs on the net? what other techniques are there? and when should they be used? ( when is it better to not use messaging?)

[Xmas79]

Messaging is the base. Without a message, how can a program understand what the remote one is just saying?

[persian_83]

as far as i know , messaging can only be used on microsoft servers, so there must be some other kind of things for applications that run on different OS....any idea?!

[Xmas79]

Sorry, no...

[persian_83]

so any one else? any idea? ( actually i'm using win2000 server, the main question is when should we use and when should we not use messaging, and what should we use in the situations that messaging is not good to be used?)

[powdir]

MSMQ can only be used on MS servers but there are other products around if you need cross-OS messaging i.e. TIBCO, Java Messaging etc. Whether or not to use messaging realy depends on the nature of the app - if network failure should occur and you loose data would this create a HUGE problem, if yes then messaging is a good option, otherwise you can always restore static data from a backup.

[Slow_Learner]

It should be noted that TIBCO is horribly expensive (don't know about Java Messaging)

[powdir]

TIBCO is horribly expensive

Damn right....

I have also found it to be a little resource hungry at times and ensuring messages arrive in the same order that they left can be quite a skill.

persian_83, i would suggest that unless your app must absolutely NOT loose data (say real time financial) just use a sensible chain of command posts and backup files to get the job done.

Cheers

[persian_83]

yeah i guess wont use messaging since data loss is not such i big deal in this case. what about performance? messaging vs databases?????