Hi guyz…I need your help a bit.. All the IT users (specially those who know programming) please help me out… Thanks
The title says enough i guess…but i will give you more details… I need to get this work done asap, i have done research on it but cant seem to get the right information… The questions is simple “How an Operating System can be viewed as an Event Driven Application?”…I dont get it…
The OS responds to any given event right? . . . So you can save a file and it causes the file to be written to disk, you list the files in a directory..This is right haina? but i need more informatio on it… Please help me out thanks!
Re: How can OS be viewed as an Event Driven Application?
I’m assuming that you’re referring to general Computer Operating Systems and not Real-Time RTOS or Embedded OS.
To answer this question, you need to refer to the concepts of priority scheduling, preemptive multi-tasking, user mode and kernel mode features of OS, and finite state mechanisms associated with multi-threading.
To get you started, in most modern day Operating Systems, event driven design is incorporated in the form of priority scheduling. Especially, with preemptive scheduling, the OS can temporarily suspend a current task, act upon another higher priority event, and resume the suspended tasks. Also, many OSs today handle processes and the respective CPU and I/O scheduling through an event scheduling hierarchy of some sort.
Re: How can OS be viewed as an Event Driven Application?
Expounding on What LC said above. The performance , memory management , disk space management , CPU management are all done by OS they are all event driven processes.
Re: How can OS be viewed as an Event Driven Application?
LC gave an excellent over views of bare bone structure of OS.
Mirch has really good approach towards application.
I assumed you are going to do an assignment?
Any answer would be right as long as you show you understanding of OS.
I just gave you 3rd place you may want to look at. As a starting point.
interrupt are the signals initiated from (normally) in put devices. It gets processors attention immediately.
So in a way its an event too.
LC gave an excellent over views of bare bone structure of OS.
Mirch has really good approach towards application.
I assumed you are going to do an assignment?
Any answer would be right as long as you show you understanding of OS.
I just gave you 3rd place you may want to look at. As a starting point.
interrupt are the signals initiated from (normally) in put devices. It gets processors attention immediately.
So in a way its an event too.
Yeah i am doing an assignment, thanks for the idea, will have a look at it :)
Array the assignment is like 10 pages long… I have done everything but i couldnt this part…thats why i asked for ur help… Please Mirch bahi if you know it than let me know… Thanks i will appreciate it!
Re: How can OS be viewed as an Event Driven Application?
Event driven programming is just pure fun. Even now I am working on an application that is event driven and NOT thread based. Ok here is the basic concept of Event driven programming. Think of it as throwing a ball and catching a ball.
Now in an application we keep on tossing this ball around and we don’t have to worry about that what catcher will do with that ball. Similarly, when work is done, ball is thrown back to us. Advantage is less overhead for us. We don’t have to worry all the time that who gona catch our ball, how they will do it and what they gona do with it.
Ok now in more technical lingo. In an OS we have multiple applications running at a time. Doing different things. Its really hard to synchoronize them and keep track of them. So instead of generating new threads/ processes, let them do the work and kill them, We just generate an Event for already existing process. This process will catch the event, will perform the action and will again generate an event to let us know that processes has been completed with these results.
I think uptill here I might have answered your question that why we use event driven programming in operating systems. I would suggest that write few programs in both Windows and Unix/Linux environment and see how they communicate using events, interrupts and signals. They are pretty cool concepts.
Re: How can OS be viewed as an Event Driven Application?
NaMaan thanks for the help... In more clear words just tell me what is
"*suitability of an event driven programs for non graphical applications, any idea?" *
I dont get this, if u know it than help me out thanks.....
Re: How can OS be viewed as an Event Driven Application?
First of all events are not only hardware driven. Study about software interrupts and hardware interrupts.
So as I understand your question you are talking about a software with no hardware interaction means no mouse clicks no key presses and stuff. Am I right ? i.e. Like a service .
First of all events are not only hardware driven. Study about software interrupts and hardware interrupts.
So as I understand your question you are talking about a software with no hardware interaction means no mouse clicks no key presses and stuff. Am I right ? i.e. Like a service .
NaMaan to be honest even i dont get it myself, i guess it is what u are saying.... probably....