https://wiki.kram.nz/index.php?action=history&feed=atom&title=SE401%3AGroup33%3AResearch%3AMark%3ADeveloping_Web_ServicesSE401:Group33:Research:Mark:Developing Web Services - Revision history2026-04-19T13:57:56ZRevision history for this page on the wikiMediaWiki 1.45.3https://wiki.kram.nz/index.php?title=SE401:Group33:Research:Mark:Developing_Web_Services&diff=11116&oldid=prevMark: 16 revision(s)2008-11-03T05:21:47Z<p>16 revision(s)</p>
<p><b>New page</b></p><div>==Developing Web Services==<br />
IEEE Exp. DB.<br /><br />
Title: Developing Web Services<br /><br />
A: Adam Bosworth {Crossgain Corporation}<br />
===Page 1===<br />
*Web Services have arisen to componentise(I may have invented a word here!) Web applications.<br />
*Web services emergence has been hindered by cost.<br />
*Web services provides a ''service'' over Internet protocols, for another program to use.<br />
*[ Examples of web services ]<br />
===Page 2===<br />
*IP is asynchronous and unreliable.<br />
*Web services can :''"increase the speed or service reliability because messaging processing does not assumes an unreliable communications infrastructure."'' - ##How will we impact on these##<br />
** The classic telephone-mail metaphor. Mail: Message could be delivered even if the service is unavailable. Messages can be sent without the need for feedback.<br />
** ''"Loosely coupled services are often required for Web Services due to the uncertainties"'' - ##What will bring down our system, can it offer any guarantees..##<br />
'''Section 2.2 - Service should Support Dynamic Hardware Scaling'''<br />
*Where one machine can not cope with the load, more machines are added (with possible separation of duties with regard to database logic, handling requests etc.)<br />
<br />
===Page 3===<br />
*Problems to solve in the multi server architecture.<br />
*#Dynamic Load Balancing<br />
*#Hardware Scaling<br />
*#Inter-Enterprise Integration Service</div>Mark