• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content

Loading…

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

Like this presentation? Why not share!

RIA 08 - AJAX and jQuery

on

  • 1,586 views

 

Statistics

Views

Total Views
1,586
Views on SlideShare
1,368
Embed Views
218

Actions

Likes
0
Downloads
54
Comments
0

2 Embeds 218

http://blog.johanneshoppe.de 217
http://paper.li 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    RIA 08 - AJAX and jQuery RIA 08 - AJAX and jQuery Presentation Transcript

    • STUDIEREN
      UND DURCHSTARTEN.
      Author: Dip.-Inf. (FH) Johannes Hoppe
      Date: ?
    • RIA – Rich Internet Applications
      Author: Dip.-Inf. (FH) Johannes Hoppe
      Date: ?
    • 01
      Message Exchange Patterns
      01.12.2010
      Folie 3
    • Message Exchange Patterns
      General
      I use Microsoft terminology which bases on
      SOAP terminology
      I will only introduce the most common patterns
      Patterns are always general solutions
      and do not relay on a special platform or transport protocol!
      Book recommendations:
      Tanenbaum / Steen: Distributed Systems: Principles and Paradigms
      Lowy: Programming WCF Services
      01.12.2010
      Folie 4
    • Message Exchange Patterns
      Request-Reply
      01.12.2010
      Folie 5
      Most common:
      Client issues a request in the form of a message, and blocks until he gets the reply message.
    • Message Exchange Patterns
      One-Way
      01.12.2010
      Folie 6
      Fire-and-forget:
      Client issues the call, but no correlated reply message willever return to the client.
      (Except network errors)
    • Message Exchange Patterns
      Duplex (callback)
      01.12.2010
      Folie 7
      2x One-Way:
      Both parties have a server roleand can call each other.
    • „Classic“ Surfing (Synchronous Dataflow)
      01.12.2010
      Folie 8
      page1.php
      page2.php
      page3.php
      Data processing...
      Data processing…
    • Message Exchange Patterns
      Discussion:
      Whichpatternisusedfor AJAX?
      01.12.2010
      Folie 9
    • Asynchronous Dataflow
      01.12.2010
      Folie 10
      Data processing...
      Data processing…
      Data processing...
      Data processing...
    • Message Exchange Patterns
      AJAX
      01.12.2010
      Folie 11
      • Request-Replaythat is not blocking the browser’s UI(by using on separate thread!)
      • W3C: XMLHttpRequest
      • According to HTTP/1.1, a client should only
      have two connections open to one host at the same time
       Own queuing has to be implemented!
    • Message Exchange Patterns
      Questions?
      ?
      01.12.2010
      Folie 12
    • 02
      Protocols and Formats
      01.12.2010
      Folie 13
    • Protocolsand Formats
      Endpoint
      is the fusion of the Address, Binding and Contract
      01.12.2010
      Folie 14
      Example:
      • A – http://test.com/service
      • B – HTTP
      • C – Methods to call
      • “Explicit style”: WSDL + SOAP
      • “Implicit style”: REST / JSON
    • Protocolsand Formats
      01.12.2010
      Folie 15
      SOAP
    • Protocolsand Formats
      01.12.2010
      Folie 16
      REST
    • Protocolsand Formats
      SOAP: Simple Object Access Protocol
      for Remote Procedure Calls, standardized but complex
      Implements a webservice
      Bases on XML (much traffic)
      On top of HTTP / HTTPS
      URI usually stays unchanged, GET: http://test.com/service
      Hard to implement “by hand”
      WSDL: Web Services Description Language
      Meta Language
      Describes webservice’s methods
      Bases on XML (much traffic)
      Hard to implement “by hand”
      01.12.2010
      Folie 17
    • Protocolsand Formats
      01.12.2010
      Folie 18
      “REST is an architectural style that is only present when all of itsconstraints are met.”
      Thomas Roy Fielding, 2003 on http://tech.groups.yahoo.com/group/rest-discuss/message/3623
    • Protocolsand Formats
      REST: Representational State Transfer
      Paradigm change: describes a very simple architecture with known standards
      Implements a webservice
      Note: there is no "official" standard for RESTful web services
      Uses HTTP / HTTPS verbs
      URI changes, eg.
      GET: http://test.com/service
      PUT: http://test.com/service/1
      POST: http://test.com/service/1
      DELETE: http://test.com/service/1
      Easy to implement “by hand”
      Usually JSON is used as the “protocol” for transferring data (few traffic)
      01.12.2010
      Folie 19
    • Protocolsand Formats
      JSON: JavaScript Object Notation
      Used for serializing data
      Lightweight and text-based
      bases on a subset of the JavaScript programming language
      Uses the object-style (key:value) and array-style notation
      Elements: Number, String, Boolean, Arrays [], Object {} and null
      01.12.2010
      Folie 20
    • Protocolsand Formats
      JSON: JavaScript Object Notation
      01.12.2010
      Folie 21
      {
      "Name": "Johannes Hoppe",
      "Address":
      {
      "Street": "Musterstraße 1",
      "City": "Musterstadt",
      "PostalCode": "12345",
      "Country": "Germany"
      },
      "Dogs": [ "Abby", "Ronja" ]
      }
    • Protocolsand Formats
      Firebug
      01.12.2010
      Folie 22
    • Protocolsand Formats
      Questions?
      ?
      01.12.2010
      Folie 23
    • 03
      jQuery
      01.12.2010
      Folie 24
    • THANK YOU
      FOR YOUR ATTENTION
      01.12.2010
      Folie 25