CushionTheBlow (구 BluemoonSoft)

내가 아는 Uno는 피자집 밖에 없는데.

아는 사람이 물어서 궁금해서 찾아봤다.

Uno stands for Universal Network Objects. Uno is one of the accepted projects of OpenOffice.org.

Uno is the component model of OpenOffice.org. Uno offers interoperability between programming languages, other components models and hardware architectures, either in process or over process boundaries, in the Intranet as well as in the Internet. Uno components may be implemented in and accessed from any programming language for which a Uno implementation (AKA language binding) and an appropriate bridge or adapter exists.

The Uno web is organized as described in Uno/Meta/Organization.

Probably most interesting for many people is, what we are currently doing in Uno, which you can find in the efforts area. One of the bigger things is the extension of Binary Unos threading-model.

언제쯤 똑똑해지는 날이 올까?



Reference:
http://udk.openoffice.org/

JBoss Application Server (or JBoss AS) is a free software / open source Java EE-based application server. Because it is Java-based, the JBoss application server is cross-platform, usable on any operating system that Java supports.

Reference:
http://en.wikipedia.org/wiki/Jboss

In n-tier architecture an application server is a server that hosts an API to expose Business Logic and Business Processes for use by other applications [1]. The term can refer to:

1. The Services that are made available by the server
2. The Computer Hardware on which the Services are deployed
3. The Software framework used to host the Services such as JBoss application server or Oracle Application Server

Reference:
http://en.wikipedia.org/wiki/Application_server

Model-driven architecture (MDA) is a software design approach for the development of software systems. It provides a set of guidelines for the structuring of specifications, which are expressed as models. Model-driven architecture is a kind of domain engineering, and supports model-driven engineering of software systems. It was launched by the Object Management Group (OMG) in 2001.

Overview
The Model-Driven Architecture approach defines system functionality using a platform-independent model (PIM) using an appropriate domain-specific language.

Then, given a platform definition model (PDM) corresponding to CORBA, .NET, the Web, etc., the PIM is translated to one or more platform-specific models (PSMs) that computers can run.

The PSM may use different Domain Specific Languages, or a General Purpose Language like Java, C#, PHP, Python, etc. Automated tools generally perform this translation.

The OMG organization provides rough specifications rather than implementations, often as answers to Requests for Proposals (RFPs). Implementations come from private companies or open source groups.

MDA principles can also apply to other areas such as business process modeling where the PIM is translated to either automated or manual processes.

Reference:
http://en.wikipedia.org/wiki/Model-driven_architecture

Hibernate is an object-relational mapping (ORM) library for the Java language, providing a framework for mapping an object-oriented domain model to a traditional relational database. Hibernate solves Object-Relational impedance mismatch problems by replacing direct persistence-related database accesses with high-level object handling functions. The Hibernate 2.1 framework won a Jolt Award in 2005. [1]

Hibernate is free as open source software that is distributed under the GNU Lesser General Public License.

Reference:
http://en.wikipedia.org/wiki/Hibernate_(Java)

The object-relational impedance mismatch is a set of conceptual and technical difficulties which are often encountered when a relational database management system is being used by a program written in an object-oriented programming language or style; particularly when objects and/or class definitions are mapped in a straightforward way to database tables and/or relational schemata. This practice has been recommended and documented by some object-oriented literature as a way to use databases in object-oriented programs.

The term Object-relational impedance mismatch is derived (etymologically) from the electrical engineering term impedance mismatch.

Reference:
http://en.wikipedia.org/wiki/Object-Relational_impedance_mismatch

In computer science, persistence refers to the characteristic of data that outlives the execution of the program that created it. Without this capability, data only exists in RAM, and will be lost when the memory loses power, such as on computer shutdown.

Computer programming
In programming, persistence refers specifically to the ability to retain data structures between program executions, such as, for example, an image editing program saving complex selections or a word processor saving undo history.

This is achieved in practice by storing the data in non-volatile storage such as a file system or a relational database or an object database. Design patterns solving this problem are container based persistence, component based persistence and the Data Access Object model. When first introduced, the idea was that persistence should be an intrinsic property of the data, in contrast with the traditional approach where data is read and written to disk using imperative verbs in a programming language. This emphasis has largely disappeared, resulting in the use of persist as a transitive verb: On completion, the program persists the data. Examples of persistence are using Java serialization to store Java objects on disk or using Java EE to store Enterprise Java Beans in a relational database.

Persistence Services
Persistence services is when the workflow runtime engine semantics dictate that persistence should occur, the workflow runtime engine will call methods supplied by a persistence service to save state information about the workflow instance. Likewise when workflow runtime engine needs to restore a previously persisted workflow instance, it will call methods supplied by the persistence service to load this state information.

Reference:
http://en.wikipedia.org/wiki/Persistence_(computer_science)