| Title: 2.1.2 - Client Architecture |
| NavPrev: ch2.1.1-server-architecture.html |
| NavPrevText: 2.1.1 - Server Architecture |
| NavUp: ch2.1-application-architecture.html |
| NavUpText: 2.1 - Application Architecture |
| NavNext: ch2.1-application-architecture.html |
| NavNextText: 2.1 - Application Architecture |
| Notice: Licensed to the Apache Software Foundation (ASF) under one |
| or more contributor license agreements. See the NOTICE file |
| distributed with this work for additional information |
| regarding copyright ownership. The ASF licenses this file |
| to you under the Apache License, Version 2.0 (the |
| "License"); you may not use this file except in compliance |
| with the License. You may obtain a copy of the License at |
| . |
| http://www.apache.org/licenses/LICENSE-2.0 |
| . |
| Unless required by applicable law or agreed to in writing, |
| software distributed under the License is distributed on an |
| "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY |
| KIND, either express or implied. See the License for the |
| specific language governing permissions and limitations |
| under the License. |
| |
| |
| # 2.1.2 - Client Architecture |
| |
| |
| We had a brief look at MINA based Server Architecture, lets see how Client looks like. Clients need to connect to a Server, send message and process the responses. |
| |
|  |
| |
| * Client first creates an IOConnector (MINA Construct for connecting to Socket), initiates a bind with Server |
| * Upon Connection creation, a Session is created and is associated with Connection |
| * Application/Client writes to the Session, resulting in data being sent to Server, after traversing the Filter Chain |
| * All the responses/messages received from Server are traverses the Filter Chain and lands at IOHandler, for processing |
