자바 웹 어플리케이션에 대해서 매우 정리가 잘 되어 있는 글이다.
추가로 서블릿에 대해서도 함께 정리해 보면,
Servlets are server side components that provide a powerful
mechanism for developing server side programs. Servlets
provide component-based, platform-independent methods for
building Web-based applications, without the performance
limitations of CGI programs. Unlike proprietary server
extension mechanisms (such as the Netscape Server
API or Apache modules), servlets are server as well as
platform-independent. This leaves you free to select a "best
of breed" strategy for your servers, platforms, and tools.
Using servlets web developers
can create fast and efficient server side application
which can run on any servlet enabled web server. Servlets
run entirely inside the Java Virtual Machine. Since the
Servlet runs at server side so it does not checks the
browser for compatibility. Servlets can access the entire
family of Java APIs, including the JDBC API to access
enterprise databases. Servlets can also access a library of
HTTP-specific calls, receive all the benefits of the mature
java language including portability, performance,
reusability, and crash protection. Today servlets are the
popular choice for building interactive web applications.
Third-party servlet containers are available for Apache Web
Server, Microsoft IIS, and others. Servlet containers are
usually the components of web and application servers, such
as BEA WebLogic Application Server, IBM WebSphere, Sun Java
System Web Server, Sun Java System Application Server and
Servlets are not designed for a specific protocols. It is
different thing that they are most commonly used with the
HTTP protocols Servlets uses the classes in the java
packages javax.servlet and javax.servlet.http. Servlets
provides a way of creating the sophisticated server side
extensions in a server as they follow the standard framework
and use the highly portable java language.
- performance limitations of CGI programs.
- JSP vs Servlet
View 가 필요없는 서비스일 경우엔 바로 Servlet으로 구현하고, View 가 필요한 서비스일 경우엔 JSP 를 활용.
<make a local repository at root folder of project: do it once>
<check that all files are tracked or not, modified, end so on>
<add files that should be added or updated>
git add test.txt
<commit add or change into local repository>
git commit -m "2nd"
<check its status and log>
<add remote repository: do it once>
git remote add origin https://github.com/username/tutorial.git
<publish local commits to remote>
git push -u origin master
When a programmer executes the following make from README file, he may have a compile error related on 'size_t' of
"cd ../libfree # continue building the basic library
Solution : Refer this site.
(replace size_t with socklen_t)
Then you execute 'make' without other error.