| | |
message passing interfaces
![]() |
Please reffer to your post about networking stuff for my answer.
http://www.daniweb.com/techtalkforums/thread8956.html
Hey,give details.There are a lot of message passing interfaces types related to various totally diffrent stuff........
http://www.daniweb.com/techtalkforums/thread8956.html
Hey,give details.There are a lot of message passing interfaces types related to various totally diffrent stuff........
•
•
•
•
Originally Posted by FireNet
Please reffer to your post about networking stuff for my answer.
http://www.daniweb.com/techtalkforums/thread8956.html
Hey,give details.There are a lot of message passing interfaces types related to various totally diffrent stuff........
if there r any links u could fwd me, thatl be gr8 too.
regards,
naveen
ps: sorry for the trouble caused if any :-)
Gee,if you want just an overall stuff about things you dont know then try http://www.google.com
That will give you lots of good stuff,as I always say enough to drown in.
P.S If you want a tut on winsock servers try the tut fourm here at daniweb.
That will give you lots of good stuff,as I always say enough to drown in.
P.S If you want a tut on winsock servers try the tut fourm here at daniweb.
In short, message passing interfaces are one of the popular ways that operating systems work.
Your code, as an application, has 'messages' "rain down" upon it. You get to respond to each message as it comes in.
Messages may be things like startup, shutdown, draw yourself, a timer fired, etc.
Some OS', like DOS, don't use message passing, instead your program assumes overall control of the computer and you demand/ask for information from the system. Console apps often work this way too.
So, a console app might say:
print "What is your name?";
input name;
if (name == "Chainsaw") print "You are a genius!";
whereas a message passing interface would be more like...
<display form>
<wait for messages>
<on edit-box-exit, get edit-box-contents, if contents == "Chainsaw", etc etc etc>
So, message passing interfaces are more involved, but allow multiple processes to share the machine cooperatively.
Your code, as an application, has 'messages' "rain down" upon it. You get to respond to each message as it comes in.
Messages may be things like startup, shutdown, draw yourself, a timer fired, etc.
Some OS', like DOS, don't use message passing, instead your program assumes overall control of the computer and you demand/ask for information from the system. Console apps often work this way too.
So, a console app might say:
print "What is your name?";
input name;
if (name == "Chainsaw") print "You are a genius!";
whereas a message passing interface would be more like...
<display form>
<wait for messages>
<on edit-box-exit, get edit-box-contents, if contents == "Chainsaw", etc etc etc>
So, message passing interfaces are more involved, but allow multiple processes to share the machine cooperatively.
![]() |
Similar Threads
- How is 3Tier architecture implemented in ASP.NET (ASP.NET)
- c vs c++ (C++)
- Ethereal Error Message (Networking Hardware Configuration)
- Error message when passing property changes between forms (VB.NET)
- Array limit (C)
Other Threads in the C Forum
- Previous Thread: problem with convert jumbled text file to unjumbled text file
- Next Thread: c lang doubts
| Thread Tools | Search this Thread |
#include * adobe ansi array arrays asterisks binarysearch centimeter changingto char character cm convert copyimagefile cprogramme creafecopyofanytypeoffileinc createprocess() database dynamic execv feet fgets file floatingpointvalidation fork function getlogicaldrivestrin givemetehcodez global grade gtkwinlinux hacking histogram inches include incrementoperators infiniteloop input interest intmain() iso kernel keyboard kilometer km linked linkedlist linux locate looping lowest matrix meter microsoft mqqueue number oddnumber open opendocumentformat openwebfoundation owf pattern pdf performance pointer posix power probleminc process program programming radix recursion recv recvblocked research reversing segmentationfault sequential single socket socketprograming socketprogramming standard strchr string suggestions systemcall test threads turboc unix urboc user variable voidmain() wab whythiscodecausesegmentationfault windowsapi





