Difference between revisions of "Client Server Model"
(→XML vs JSON) |
(→XML vs JSON) |
||
| Line 19: | Line 19: | ||
==XML vs JSON== | ==XML vs JSON== | ||
| − | + | WESTY IS A WEEB | |
| − | |||
{| class="wikitable" border="1" | {| class="wikitable" border="1" | ||
|- | |- | ||
Revision as of 14:21, 13 March 2017
Contents
Response & Request
API
An API or Application Program Interface is a set of routines enabling one program to interface with each other. The code defines how the programs work together.
Twitter has an API to allow other programs to use the service.
WebSockets Protocol
CRUD
daddy
REST
JSON
XML
WIP
XML vs JSON
WESTY IS A WEEB
| JSON | XML | |
|---|---|---|
| Human Readable | It's easy to read because it's just defining objects and values. | Less readable because it's contained within markup tags |
| Compact Code | Less code than XML | More code than JSON |
| Speed of Parsing | Quicker, because it's defined as object and value | Slower, because the data has to be extracted from tags |
| Ease of Creation | Easier, because syntax is easier | More like programming so more knowledge is needed. |
| Flexibility & Extendibilty | Only works with limited data types, not enough for all applications | Gives total freedom, because you can create what data types there are, so it has greater flexibility |
