Delving into the Dalvik VM

Gogle has spent a lot of time thinking about optimizing designs for low-powered handheld devices.

Handheld devices lag begind their desktop counterparts in memory and speed by eight to ten years.

They also have limited power for computation; a handheld device's totaal RAM might be as little as 64MB, and its available space for applications might be as little as 20MB.

The performance requirements on handsets are severe as

Oracle import / export

================================================================================ ※※※ 필수 사항 ※※※================================================================================1> export 받을때 반드시!! 데이타베이스 인스턴스의 문자셋과 동일하게 사용자의 환경변수(NLS_LANG)를 셋팅해주어야 한다.
1. 한글을 지원하는 문자셋 1-1. KO16KSC5601 1-2. KO16MSWIN949 1-3. UTF8 1-4. AL32UTF8
2. NLS_LANG 의 변수 설정방식 -> 도트(.) 다음의 변수 설정값을 DB와 동일하게 선택 ex) Korean_Korea.KO16KSC5601 ex) Korean_Korea.KO16MSWIN949 ex) American_America.KO16KSC5601 ex) American_America.UTF8
3. 확인방법 ex) select * from v$nls_parameters;
4. UNIX 의 경우 export 하기 전에 exp 유틸을 실행 시킬 계정의 .profile 에 아래 사항 셋팅 ex) export NLS_LANG=American_America.KO16KSC5601
5. WINDOW 의 경우 export 하기 전에 셋팅 ex) set NLS_LANG=Korean_Korea.KO16MSWIN949
2> 덤프/로그 파일명 명명 규칙
1. 덤프 파일명 => 일시_기관코드_유저명(or table)_data(or schema)_순번.dmp
1-1. user 별로 스키마만 export 할 경우 ex) 20060512_Tong01_statdb_schema_01.dmp
1-2. user 별로 스키마+데이타를 export 할 경우 ex) 20060512_Tong01_statdb_data_01.dmp
1-3. table 별로 스키마만 export 할 경우 ex) 20060512_Tong01_table_schema_01.dmp
1-4. table 별로 스키마+데이타를 export 할 경우 ex) 20060512_Tong01_table_data_01.dmp
2. 로그 파일명 => 실행명(exp/imp/shw)_덤프파일명.log
2-1. export 실행 ex) exp_20060512_Tong01_statdb_schema_01.log
2-2. import 전에 분석 작업 실행 ex) shw_20060512_Tong01_statdb_schema_01
2-3. import 실행 ex) imp_20060512_Tong01_statdb_schema_01
3> [권고사항] export는 user별로 받는다!!
4> import 전에 import 할 대상 user는 생성되어 있어야 된다!! (user별 tablespace는 지정되어 있어야 된다.)
5> export/inport시 속도 향상을 위해 index는 로드하지 않고 리빌드 한다.(옵션 : indexes=n) 리빌드 명령어 : alter index scott.IDX_DD_TST_TAB_NO rebuild
6> import 시 tables=(*) 옵션을 주게 되면 synonym/view..등의 오브젝트는 빠지고 table만 import된다.
7> exp/imp 옵션은 적절히 이용.. 단 import 시에 ignore=y 옵션 사용을 하게 되면 추가로 데이터가 들어가기 때문에, sourceDB 와 targetDB의 데이터를 동기화 시킬 필요가 있을시에는 targetDB의 테이블 데이타를 삭제후 import한다.
================================================================================ ※※※ user별 스키마만 export/import 사용 예 ※※※================================================================================1> exp system/manager@sourceDB owner=statdb file=20060512_Tong01_statdb_schema_01.dmp log=exp_20060512_Tong01_statdb_schema_01.log rows=n
2> imp system/manager@targetDB fromuser=statdb touser=scott file=20060512_Tong01_statdb_schema_01.dmp log=shw_20060512_Tong01_statdb_schema_01.log show=y
3> imp system/manager@targetDB fromuser=statdb touser=scott file=20060512_Tong01_statdb_schema_01.dmp log=imp_20060512_Tong01_statdb_schema_01.log rows=n grants=n resumable=y tables=(*)
================================================================================ ※※※ user별 스키마+데이타 export/import 사용 예 ※※※================================================================================1> exp system/manager@sourceDB owner=statdb file=20060512_Tong01_statdb_data_01.dmp log=exp_20060512_Tong01_statdb_data_01.log rows=y grants=n indexes=n
2> imp system/manager@targetDB fromuser=statdb touser=scott file=20060512_Tong01_statdb_data_01.dmp log=shw_20060512_Tong01_statdb_data_01.log show=y
3> imp system/manager@targetDB fromuser=statdb touser=scott file=20060512_Tong01_statdb_data_01.dmp log=imp_20060512_Tong01_statdb_data_01.log rows=y ignore=y grants=n resumable=y commit=y indexes=n tables=(*)
================================================================================ ※※※ table별 스키마만 export/import 사용 예 ※※※================================================================================1> exp system/manager@sourceDB tables=(statdb.cc%, statdb.dd%) file=20060512_Tong01_table_schema_01.dmp log=exp_20060512_Tong01_table_schema_01.log rows=n
2> imp system/manager@targetDB fromuser=statdb touser=scott file=20060512_Tong01_table_schema_01.dmp log=shw_20060512_Tong01_table_schema_01.log show=y
3> imp system/manager@targetDB fromuser=statdb touser=scott file=20060512_Tong01_table_schema_01.dmp log=imp_20060512_Tong01_table_schema_01.log rows=n grants=n resumable=y tables=(*)
================================================================================ ※※※ table별 스키마+데이타 export/import 사용 예 ※※※================================================================================1> exp system/manager@sourceDB tables=(statdb.cc%, statdb.dd%) file=20060512_Tong01_table_data_01.dmp log=exp_20060512_Tong01_table_data_01.log rows=y grants=n indexes=n
2> imp system/manager@targetDB fromuser=statdb touser=scott file=20060512_Tong01_table_data_01.dmp log=shw_20060512_Tong01_table_data_01.log show=y
3> imp system/manager@targetDB fromuser=statdb touser=scott file=20060512_Tong01_table_data_01.dmp log=imp_20060512_Tong01_table_data_01.log rows=y ignore=y grants=n resumable=y commit=y indexes=n tables=(*)

http://blog.naver.com/oliedolie?Redirect=Log&logNo=60045241634 에서 발췌...

1.2. What is WSIT?

1.2.1. Bootstrapping and Configuration

HelloWorld

Activity is the base class for the visul, interactive components of your application

It is roughly equivalent to a Form in traditional desktop development.

The following snippet shows the skeleton code for an Activity-based class

note that it extends Activity, overriding the onCreate method.

import android.app.Activity;

import android.os.Bundle;

public class HelloWorld extends Activity{

public void onCreate(Bundle b)

{

super.onCreate(b)

}

}

Android chapter1

android is made up of

crontab 에서 oracle exp

#!/usr/bin/cshsetenv CDATE "backup-`date +%Y-%m-%d-%H-%M-%S`"exp scott/tiger file=/oracle/exp_backup/$CDATE.dmp log=/oracle/exp_backup/$CDATE.log

. chmod 755 backup.sh4. cron 등록- root 로 로그인 -#crontab -e

1.3 스트럿츠 2 프레임워크

Struts 2 is a brand new, state of the art web application framework. As we said ealier, Strtuts2 is not just a new release of the older Struts 1 framework. It is a completely new framework, based on the architecturally esteemed WebWork framework. By now you should be pretty tuned in to what a web application framework should offer. In terms of the common domain tasks, Struts2 covers the domain quite well. It handles all of the tasks we have identified, and more. During the course of the book, you will learn how to work with the features that address each of those tasks in turn, At the introductory stage fo things, it makes more sense to focus on the architectuarl aspects of the framework. So in this section, we will look at the dsign pattern roots of Struts 2, see how those roots influence the high level architectu4re, and take a slightly more detaied look at how the framework handles actual request processing.

1.3.1 간단한 역사
Struts 2 is a second generation web application framework that implements the Mdel-View-Controller(MVC) desing patten. Struts 2 is built form the ground up on best practices and proven, community accepted design patterns. This was true for the first version of Struts as well. In fact, one of the primary goal of the first Struts was the incorporation of the Model-View-Controller(MVC)pattern into a web application framework. This was, of course, a critical step in th evolutino of well designed web applications as it provided th infrastructure of making the MVC separeation fo concerns n easily achived goal. This allowed developers, with little resources for such architectural niceties, to tap into a ready made best practice solution. Struts 1 can certainly claim responsibility for many of the more well designed web applications of the lkast ten years.

At some point, the Struts community became aware of the limitations in the first framework. With such an active community, identification of the weak and inflexible points in to present a cleaner implementation of MVC. At the same time, it intruduces serverl new architectural features that make the framework cleaner and more flexible. These new features include such thisng as interceptors for layering cross cutting concerns away from action logic, annotation based configuration to reduce classpath pollution, a powerful expression language OGNL that transverses the en