|
|
|
| Authored by: Anonymous on Monday, April 23 2012 @ 05:07 PM EDT |
And the undocumentd things in an API are the off-menu items one can order
at the eating establishment.[ Reply to This | Parent | # ]
|
| |
| Authored by: SpaceLifeForm on Monday, April 23 2012 @ 08:26 PM EDT |
Actually, it is more complex than that.
Your main object is the waitress.
You request a list (menu items) from the waitress.
(depending upon the service, that is implied as soon
as you sit down, but a drive thru, the list may be
on a board. Sometimes, you may have to ask anyway
at a sitdown establishment. Sometimes, they know you
are not going to eat).
You then repeatedly interact via calls the waitress
requesting items from the menu list.
Each call to the waitress can result in an exception.
Sorry, we are out of that today.
A call to the waitress function may be a request for
more information, ex: What is the special today?
Each call to the waitress function may result in the
waitress adding items from the list menu to another list,
the order list.
At some point, you tell the waitress that you have no
more items to add to the list.
The order list may be empty at this point too.
If the order list is not empty, the waitress function
place order occurs. This is the magic, the implementation,
that you normally do not have the source code to.
If you are in a real dive, you likely don't want to
see the secret sauce code.
At some time later, the waitress returns with
some output. Hopefully, it is good.
---
You are being MICROattacked, from various angles, in a SOFT manner.[ Reply to This | Parent | # ]
|
|
|
|
|
