http://stackoverflow.com/questions/2889777/difference-between-hashmap-linkedhashmap-and-treemap

 

https://dzone.com/articles/difference-between-hashmap-and

 

 

Advertisements

servlet

|
|first request |subsequent
| |request
| |
container |
| |
| |
loading,initializing(when deployed) |
| |
| |
init() |
| |
|<————————————–
instance of servlet(HttpRequest,HttpResponse)
|
|
Thread(HttpRequest,HttpResponse)
|
|
servise()
|
|
destroy()
|
|
deleteThread or send back to Container to reuse.

difference between ACTION_UP and ACTION_POINTER_UP

Android thinks about touch events in terms of gestures. A gesture in this sense includes all events from the first finger that touches the screen to the last finger that leaves the screen. A single gesture’s entire event sequence is always sent to the same view that was picked during the initial ACTION_DOWN unless a parent intercepts the event stream for some reason. If a parent intercepts a child’s event stream, the child will get ACTION_CANCEL.

If you’re working with multitouch events, always use the value returned by getActionMasked() to determine the action. If you don’t need multitouch or are working with an older platform version, you can ignore the ACTION_POINTER_* events.

  • ACTION_DOWN is for the first finger that touches the screen. This starts the gesture. The pointer data for this finger is always at index 0 in the MotionEvent.
  • ACTION_POINTER_DOWN is for extra fingers that enter the screen beyond the first. The pointer data for this finger is at the index returned by getActionIndex().
  • ACTION_POINTER_UP is sent when a finger leaves the screen but at least one finger is still touching it. The last data sample about the finger that went up is at the index returned by getActionIndex().
  • ACTION_UP is sent when the last finger leaves the screen. The last data sample about the finger that went up is at index 0. This ends the gesture.
  • ACTION_CANCEL means the entire gesture was aborted for some reason. This ends the gesture.