Video Format

MPEG-4

H.264

Ogg Theora

WebM

CMS

Drupal
PHP

Wordpress

Joomla

Android Activity and task

A task is a collection of activities that users interact with when performing a certain job. The activities are arranged in a stack (the "back stack"), in the order in which each activity is opened.
A task is a cohesive unit that can move to the "background" when users begin a new task or go to the Home screen, via the HOME key.

When the system stops one of your activities (such as when a new activity starts or the task moves to the background), the system might destroy that activity completely if it needs to recover system memory. The system's default behavior preserves the state of an activity when it is stopped. This way, when users navigate back to a previous activity, its user interface appears the way they left it. However, you can—and should—proactively retain the state of your activities using callback methods(onSaveInstanceState()), in case the activity is destroyed and must be recreated.

Mablab

http://blog.163.com/zjg0202@126/blog/static/57519237200961798917/

svn commands

1. Check updated uncommit local files
svn status -u

SVG

How to change text in SVG via external javascript

var elem = document.getElemetById("textElem"); // Assuming textElem is the id of text object in SVG.
textElem.firstChild.nodeValue = "Nex Text Here";

How the SVG was loading the javascript. Assuming WebKit-based browsers, I had to link the external javascript file from inside the SVG, not the HTML document (which wouldn't work). In HTML, I used:

//Then inside the SVG file, I linked the js file, and added an onload event, which happens after parsing, before rendering:

Then inside the javascript file:

function init(evt) {
// sample call
     changeText("change my text");

}

function changeText(value) {
    var svgText;
    svgText = document.getElementById("varMyData").firstChild;
    svgText.nodeValue = value;
}

Session management

There are three widely used methods for maintaining sessions in web environment: URL arguments, hidden form fields and cookies. While each of them has its benefits and shortcomings, cookies have proven to be the most convenient and also the least insecure of the three.

The "storage" of session IDs and the associated session data (user name, account number, etc.) on the web server is accomplished using a variety of techniques including, but not limited to: local memory, flat files, and databases.



To mitigate this particular threat (though not the XSS problem in general), many web applications tie session cookies to the IP address of the user who originally logged in, and only permit that IP to use that cookie. This is effective in most situations (if an attacker is only after the cookie), but obviously breaks down in situations where an attacker spoofs their IP address, is behind the same NATed IP address or web proxy—or simply opts to tamper with the site or steal data through the injected script, instead of attempting to hijack the cookie for future use.