Difference between revisions of "User:Bartholomew Kleiber"
(addes OAuth and XMPP references) |
(addes reference to my serious games whitepaper) |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 5: | Line 5: | ||
Dirk Krause/Bartholomew Kleiber | Dirk Krause/Bartholomew Kleiber | ||
[http://www.pixelpark.com/de/pixelpark/_ressourcen/attachments/publikationen/080529_White_Paper_Serious_Games_English_final.pdf] | |||
Serious Games Whitepaper | |||
--------------------- | --------------------- | ||
| Line 11: | Line 12: | ||
--------------------- | --------------------- | ||
very | very interesting XEP here: | ||
[http://www.xmpp.org/extensions/xep-0235.html] | [http://www.xmpp.org/extensions/xep-0235.html] | ||
| Line 22: | Line 23: | ||
[http://oauth.net/code] | [http://oauth.net/code] | ||
C# and python implementation among others. | C# and python implementation among others. | ||
[http://www.thomas-guettler.de/vortraege/zodb/einfuehrung.html] | |||
German ZODB introduction. | |||
[http://www.scribd.com/doc/193634/Jabber-Inc-SIP-RTP-XMPP-White-Paper?autodown=pdf] | |||
Jabber Inc SIP RTP XMPP White Paper (ePaper) | |||
[http://www.jabber.com/CE/WhitePapers] | |||
http://www.jabber.com/CE/WhitePapers | |||
[http://www.sipcenter.com/sip.nsf/html/Whitepapers] | |||
General SIP Whitepapers | |||
Latest revision as of 13:37, 25 September 2008
A placeholder for now, more info to follow.
A short reference to the web3d-blog.
Dirk Krause/Bartholomew Kleiber
[1] Serious Games Whitepaper
References to look at
very interesting XEP here:
[2] This specification defines an XMPP extension for delegating access to protected resources over XMPP, using the OAuth protocol. In the language of OAuth, a User can authorize a Consumer to access a Protected Resource that is hosted by a Service Provider; this authorization is encapsulated in a token that the User requests from the Service Provider, that the User shares with the Consumer, and that the Consumer then presents to the Service Provider in an access request. This specification assumes that OAuth tokens will be acquired via HTTP as defined in the core OAuth specification, then presented over XMPP to a Service Provider. The Protected Resources accessible over XMPP might include groupchat rooms, data feeds hosted at publish-subscribe nodes, media relays, communication gateways, and other items of interest.
[3]
code example.
[4] C# and python implementation among others.
[5] German ZODB introduction.
[6] Jabber Inc SIP RTP XMPP White Paper (ePaper)
[7] http://www.jabber.com/CE/WhitePapers
[8] General SIP Whitepapers