Hey guys, I'm currently doing an assignment for college and I have to research programming paradigms. I need an explanation of what service oriented programming languages have to do with event driven programming but I can really make any sense of it to be honest. My lecturer doesn't really help he just says "research it online" etc etc. The information I've read online means nothing to me really as I've only really started programming.
What I've got at the minute is:
This programming paradigm uses ‘services’ within the businesses current system to create a new, faster system in which each ‘service’ is given a place in the hierarchal structure of the application. Think of a service as a task in which the company carries out every day. If you put all these services into the application in order of importance the new system should prove to be more effective. The system’s information should be able to transfer within the company effectively.
And I don't even know if any of that is correct.
Can somebody help me by explaining service oriented programming please? :'(
Thanks
2 replies to this topic
#1
Posted 27 October 2011 - 11:37 AM
|
|
|
#2
Posted 27 October 2011 - 01:33 PM
From the little I read here: Service-oriented programming - Wikipedia, the free encyclopedia I would describe it as follows.
1) write programs that are designed to run as services. For example, most databases run as a service on a server. It listens for connections, and then listens for requests and provides responses to those requests.
2) Design those programs to establish connections with each other, and use message passing as the key to performing work. For example, you might have the MySQL service running, and the Apache service running. A request is sent to the Apache service from over the internet. It, in turn, connects to the MySQL service (via a PHP script) and sends a sequence of messages. The result of processing those messages is then sent back to the requestor as an HTML page.
1) write programs that are designed to run as services. For example, most databases run as a service on a server. It listens for connections, and then listens for requests and provides responses to those requests.
2) Design those programs to establish connections with each other, and use message passing as the key to performing work. For example, you might have the MySQL service running, and the Apache service running. A request is sent to the Apache service from over the internet. It, in turn, connects to the MySQL service (via a PHP script) and sends a sequence of messages. The result of processing those messages is then sent back to the requestor as an HTML page.
#3
Posted 16 February 2012 - 11:56 AM
Okay, but what is it?
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users


Sign In
Create Account

Back to top









