This document summarizes the past, present, and future of a solo middle-aged male developer living in Jeju, Korea. It describes his experiences from first encountering computers in the 1980s, writing early code, founding startups in the 1990s and 2000s, working as a salaryman, and returning to open source development. It highlights the technologies and languages he has worked with over time, from Apple BASIC to modern tools like Java, JavaScript, and Rust. The document envisions him continuing to live in Jeju as a coding specialist into old age, emphasizing the importance of reading source code and standing on the shoulders of giants in one's field.
Basic of web ref.웹을지탱하는기술_01
1. 웹 이전의 인터넷 : 전자메일, FTP, Telnet, Gopher
2. 팀버너스리에 의해 웹이 탄생, Mosaic 브라우저를 통해 사용자 증가
3. 표준화의 필요성 > IETF, W3C등
4. SOAP vs REST 분쟁
Understand about what JSON is
Understand the difference between JSON and XML
Understand the context of using JSON with AJAX
Know how to read and write JSON data using PHP
This document discusses strategies for using Node.js alongside Java/Spring applications. It introduces J2V8, which allows running Node.js modules and the V8 JavaScript engine in Java. Examples are given for isomorphic React rendering using Nashorn or Node.js. The document also covers using Nashorn or script templating engines like EJS directly in Spring MVC. Performance benchmarks show J2V8 templating is faster than traditional Java approaches like JSP or Thymeleaf. Source code examples demonstrate setting up J2V8 with Spring Boot for building isomorphic web applications that leverage both Java and JavaScript.
This document summarizes the past, present, and future of a solo middle-aged male developer living in Jeju, Korea. It describes his experiences from first encountering computers in the 1980s, writing early code, founding startups in the 1990s and 2000s, working as a salaryman, and returning to open source development. It highlights the technologies and languages he has worked with over time, from Apple BASIC to modern tools like Java, JavaScript, and Rust. The document envisions him continuing to live in Jeju as a coding specialist into old age, emphasizing the importance of reading source code and standing on the shoulders of giants in one's field.
Basic of web ref.웹을지탱하는기술_01
1. 웹 이전의 인터넷 : 전자메일, FTP, Telnet, Gopher
2. 팀버너스리에 의해 웹이 탄생, Mosaic 브라우저를 통해 사용자 증가
3. 표준화의 필요성 > IETF, W3C등
4. SOAP vs REST 분쟁
Understand about what JSON is
Understand the difference between JSON and XML
Understand the context of using JSON with AJAX
Know how to read and write JSON data using PHP
This document discusses strategies for using Node.js alongside Java/Spring applications. It introduces J2V8, which allows running Node.js modules and the V8 JavaScript engine in Java. Examples are given for isomorphic React rendering using Nashorn or Node.js. The document also covers using Nashorn or script templating engines like EJS directly in Spring MVC. Performance benchmarks show J2V8 templating is faster than traditional Java approaches like JSP or Thymeleaf. Source code examples demonstrate setting up J2V8 with Spring Boot for building isomorphic web applications that leverage both Java and JavaScript.
2Naver Open Android API Translation At DCampJeikei Park
■ 제 목 : Naver 오픈api-android-tran-20160529
■ 주제 : 네이버 오픈API를 활용한 안드로이드 통역앱 만들기
■ 내용 :
- 통역앱 개발을 위한 네이버 오픈API 소개
- 통역앱 안드로이드 화면 구성
- 안드로이드앱에서 각 API 호출 및 처리
- 통역앱 작동을 위한 애플리케이션 처리 노하우
■ 난이도 수준: 초급
■ 발표자 소개: 옥상훈 강사
- 現 표준프레임워크 오픈커뮤니티 에반젤리스트
- 現 네이버 랩스 D2에반젤리스트
- 現 네이버 개발자센터 & 오픈 API 담당
- 前 한국Adobe 시스템즈 컨설턴트
- 前 한국 자바 개발자협의회 회장
■ 일시: 2016. 5. 31(화) 19:00~21:00(120분)
■ 장소: 디캠프 6층 다목적홀 (선정릉역 위치)
AManaging Kong API Gateway with TerraformByungjin Park
2018년 10월 23일 진행된 하시코프 한국 사용자 모임 두 번째 밋업 발표 자료 입니다.
# Terraform으로 Kong API Gateway 관리하기
박병진, Site Reliability Engineer @ Kasa
Abstract:
Kong은 Nginx와 Lua를 기반으로 하는 오픈소스 API Gateway입니다. 본 세션에서는 API Gateway가 무엇인지, Kong을 선택한 이유와 사용 방법, Terraform을 이용하여 Kong을 관리한 경험을 공유합니다.
The document discusses the process of how a browser loads a webpage from inputting a URL to displaying the content. It involves:
1. The browser parsing the input URL and checking HSTS lists to determine if a secure connection is required.
2. It uses DNS to resolve the domain name to an IP address.
3. A TCP socket connection is established between the server and router gateways.
4. An HTTP(S) request and response is made, which the browser then parses and renders the content.
2Naver Open Android API Translation At DCampJeikei Park
■ 제 목 : Naver 오픈api-android-tran-20160529
■ 주제 : 네이버 오픈API를 활용한 안드로이드 통역앱 만들기
■ 내용 :
- 통역앱 개발을 위한 네이버 오픈API 소개
- 통역앱 안드로이드 화면 구성
- 안드로이드앱에서 각 API 호출 및 처리
- 통역앱 작동을 위한 애플리케이션 처리 노하우
■ 난이도 수준: 초급
■ 발표자 소개: 옥상훈 강사
- 現 표준프레임워크 오픈커뮤니티 에반젤리스트
- 現 네이버 랩스 D2에반젤리스트
- 現 네이버 개발자센터 & 오픈 API 담당
- 前 한국Adobe 시스템즈 컨설턴트
- 前 한국 자바 개발자협의회 회장
■ 일시: 2016. 5. 31(화) 19:00~21:00(120분)
■ 장소: 디캠프 6층 다목적홀 (선정릉역 위치)
AManaging Kong API Gateway with TerraformByungjin Park
2018년 10월 23일 진행된 하시코프 한국 사용자 모임 두 번째 밋업 발표 자료 입니다.
# Terraform으로 Kong API Gateway 관리하기
박병진, Site Reliability Engineer @ Kasa
Abstract:
Kong은 Nginx와 Lua를 기반으로 하는 오픈소스 API Gateway입니다. 본 세션에서는 API Gateway가 무엇인지, Kong을 선택한 이유와 사용 방법, Terraform을 이용하여 Kong을 관리한 경험을 공유합니다.
The document discusses the process of how a browser loads a webpage from inputting a URL to displaying the content. It involves:
1. The browser parsing the input URL and checking HSTS lists to determine if a secure connection is required.
2. It uses DNS to resolve the domain name to an IP address.
3. A TCP socket connection is established between the server and router gateways.
4. An HTTP(S) request and response is made, which the browser then parses and renders the content.
Here are the key points about the WWW in the early 1990s:
- Tim Berners-Lee invented the World Wide Web in 1990 at CERN, releasing the first web browser (WorldWideWeb) and web server (CERN httpd) in 1990.
- The web used Hypertext Transfer Protocol (HTTP) for communication and Hypertext Markup Language (HTML) for documents. This allowed documents to contain links to other documents on different servers across the internet.
- Early web browsers in the 1990s included ViolaWWW (1990), Mosaic (1993), and Netscape Navigator (1994). These made the web more accessible with graphical user interfaces.
- The World Wide Web Consortium (W3C)
The document discusses the evolution of the World Wide Web from version 1.0 to 2.0. Web 1.0 utilized early technologies like HTML 3.x, HTTP 1.0 and limited JavaScript. It featured a read-only web with little user interaction. Web 2.0 saw advances in technologies that enabled a read-write web with more dynamic content and greater user engagement through features like AJAX and richer client-side scripting. However, the web was still primarily a supplemental "glue" with serverside pages and constrained interactivity. The author suggests the concepts discussed represent an emerging Web 3.0 with even more capabilities.
K모바일에서 발표한 단일 페이지 인터페이스 웹/앱 개발. 웹의 역사와 개발 패러다임의 변화를 되돌아보고, 웹앱을 위한 아키텍쳐로 단일 페이지 인터페이스(Single Page Interface)를 제시하고, jQueryMobile과 SenchaTouch를 이용해 동일한 웹앱을 SPI 방식으로 만들어본다.
Hybrid mobile applications combine native and web technologies. They use a native shell application containing a web view to display web-based UIs, allowing development with web standards like HTML, CSS, and JavaScript. This provides better performance than pure web apps while reducing costs compared to purely native apps. Popular hybrid frameworks include Titanium, PhoneGap, Rhodes, jQTouch, and iUI. They support building cross-platform mobile apps for devices like iPhone, Android, BlackBerry and more.
This document summarizes common mistakes made when writing JavaScript code. It discusses issues like asynchronous code execution, incorrect use of 'this', logical operator precedence, type comparisons, variable scope, function overloading, encoding, strings vs arrays, parseInt radix, trailing commas, framework usage, browser compatibility, and linting. The document aims to help developers avoid typical pitfalls in JavaScript programming.
This document provides an overview of the GNOME desktop environment, including its core libraries and tools for developers as well as its main applications for users. It discusses GNOME's history and goals of being a free and easy-to-use desktop. The key libraries covered include GTK+, GLib, Pango, ATK, GDK, and GNOME VFS. Important developer tools like Glade, Anjuta, and GOB are also summarized. Finally, the document outlines many of GNOME's core applications and other notable programs.
4. 눈에 보이는 API (3)
그러나...
그것은...
API 문서일 뿐...
눈에 보이는 것이...
API의 전부는 아니랍니다...
OTL
4
5. API란?
Application Programming Interface
Application Program
a program that gives a computer instructions
that provide the user with tools
to accomplish a task
Interface: inter + face; 얼굴과 얼굴 사이?!
a surface forming a common boundary
between two things
5
20. 화성인에게 API란?
외부 시스템이 내부 시스템이
제공하는 기능을 사용하기 위
해 지켜야 하는 규약 & 문서
그리고, 실제로 요청을 받고
응답을 하는 시스템의 맨 바깥
계층 & 코드 덩어리
그리고, 계층을 통해 규약에
맞춰 요청을 보내고 응답을 받
기 위한 코드 덩어리
20