TIPC for every one

This's document that I printed out for reading and taking note easily.
it talks about TICP ( telecome Inter Communication Prototol )
if you're have any question please feel free to ask

Transparent Inter Process Communication Protocol

---
name: hoang nguyen
nickname: mathhoang
Y!M: vietnam_hoangminhnguyen@yahoo.com
mail: vietnam_hoangminhnguyen@Yahoo.com
site: http://kattyflea.co.cc
---

Introduction to algorithms

This's a good book about algorithms.
It's very useful for who is studying IT or software engineering or computer science and also for who is interested in computer science.

follow below link to get this book:

http://www.mediafire.com/?6ewxudcigel

---
name: hoang nguyen
nickname: mathhoang
Y!M: vietnam_hoangminhnguyen@yahoo.com
mail: vietnam_hoangminhnguyen@Yahoo.com
site: http://kattyflea.co.cc
---

What is Piggybacking ?

Piggybacking is a bi-directional data transmission technique in the network layer (OSI model). It makes the most of the sent data frames from receiver to emitter, adding the confirmation that the data frame sent by the sender was received successfully (ACK acknowledge). This practically means, that instead of sending an acknowledgement in an individual frame it is piggy-backed on the data frame.

---
name: hoang nguyen
nickname: mathhoang
Y!M: vietnam_hoangminhnguyen@yahoo.com
mail: vietnam_hoangminhnguyen@Yahoo.com
site: http://kattyflea.co.cc
---

TIPC tutorial part 1

This's my research about TIPC => all information is just for tutorial and part 2 is comming soon.

what is TIPC?
TIPC stands for Telecom Inter Process Communication.

TIPC is a high-speed, reliable, message oriented communication service specially designed
for cluster environments. It provides complete location transparency for intra-cluster
messaging, using a concept of logical addressing and maintaining a “hot” internal address
translation table. Its ability to provide both a connectionless and a lightweight connection
oriented communication mode makes it particularly suitable for systems where short, real
time critical transactions are performed. In both communication modes it maintains a quality
of service guaranteeing no message losses, no duplicates and uninterrupted message
sequence order.

and more about it => please read the following slides ...

TIPC Introduction Part 1 created by hoang nguyen


---
name: hoang nguyen
nickname: mathhoang
Y!M: vietnam_hoangminhnguyen@yahoo.com
mail: vietnam_hoangminhnguyen@Yahoo.com
site: http://kattyflea.co.cc
---

Sliding Window Protocols

Sliding Window Protocols are a feature of packet-based data transmission protocols. They are used where reliable in-order delivery of packets is required, such as in the data link layer (OSI model) as well as in TCP (transport layer of the OSI model).

Conceptually, each portion of the transmission (packets in most data link layers, but bytes in TCP) is assigned a unique consecutive sequence number, and the receiver uses the numbers to place received packets in the correct order, discarding duplicate packets and identifying missing ones. The problem with this is that there is no limit of the size of the sequence numbers that can be required.

By placing limits on the number of packets that can be transmitted or received at any given time, a sliding window protocol allows an unlimited number of packets to be communicated using fixed-size sequence numbers.

---
name: hoang nguyen
nickname: mathhoang
Y!M: vietnam_hoangminhnguyen@yahoo.com
mail: vietnam_hoangminhnguyen@Yahoo.com
site: http://kattyflea.co.cc
---

following part 3, below is part 4 for embedded system series. If there's any unclear point or you'd like to discuss => please leave your comment or send e-mail directly to me :)



Real Time embedded system from Hoang Nguyen ( created by Nam Ho || Guider: Dinh Vu Anh Duc )

---
name: hoang nguyen
nickname: mathhoang
Y!M: vietnam_hoangminhnguyen@yahoo.com
mail: vietnam_hoangminhnguyen@Yahoo.com
site: http://kattyflea.co.cc
---

Embedded System Tutorial part 3

following part 2, below is part 3 for embedded system series. If there's any unclear point or you'd like to discuss => please leave your comment or send e-mail directly to me :)



Real Time embedded system from Hoang Nguyen ( created by Nam Ho || Guider: Dinh Vu Anh Duc )

---
name: hoang nguyen
nickname: mathhoang
Y!M: vietnam_hoangminhnguyen@yahoo.com
mail: vietnam_hoangminhnguyen@Yahoo.com
site: http://kattyflea.co.cc
---

Embedded System Tutorial part 2

following part 1, below is part 2 for embedded system series. If there's any unclear point or you'd like to discuss => please leave your comment or send e-mail directly to me :)



Real Time embedded system from Hoang Nguyen ( created by Nam Ho || Guider: Dinh Vu Anh Duc )

---
name: hoang nguyen
nickname: mathhoang
Y!M: vietnam_hoangminhnguyen@yahoo.com
mail: vietnam_hoangminhnguyen@Yahoo.com
---

Embedded System Tutorial part 1

hello all,
From now on, I will post embedded system series, these documents from Dr. Dinh Vu Anh Duc who is teaching in HCMC university of technology. You can visit his profile at :
http://www.cse.hcmut.edu.vn/~anhvu/biography.html

Real Time embedded system from Hoang Nguyen ( created by Nam Ho || Guider: Dinh Vu Anh Duc )


---
name: hoang nguyen
nickname: mathhoang
Y!M: vietnam_hoangminhnguyen@yahoo.com
mail: vietnam_hoangminhnguyen@Yahoo.com
---

Reliability Terminology

Sometimes My friends ask me to differ some definitions: System failure, System error, System fault and Human error. actually, these definitions lead me some confusion while distinguishing between them.

After spending a little time to investigate these definitions, now I can distinguish them:

System failure
An event that occurs at some point in time when the system does not deliver a service as expected by its users

System error
An erroneous system state that can lead to system behaviour that is unexpected by system users.

System fault
A characteristic of a software system that can lead to a system error. For example, failure to initialise a variable could lead to that variable having the wrong value when it is used.

Human error or mistake
Human behaviour that results in the introduction of faults into a system.

---
name: hoang nguyen
nickname: mathhoang
Y!M: vietnam_hoangminhnguyen@yahoo.com
mail: vietnam_hoangminhnguyen@Yahoo.com
---

What is CASE (Computer-Aided Software Engineering)

Software systems that are intended to provide automated support for software process activities.

CASE systems are often used for method support.

Upper-CASE
Tools to support the early process activities of requirements and design;

Lower-CASE
Tools to support later activities such as programming, debugging and testing.

---
name: hoang nguyen
nickname: mathhoang
Y!M: vietnam_hoangminhnguyen@yahoo.com
mail: vietnam_hoangminhnguyen@Yahoo.com
---

Write code in blogspot

<pre style="border: 1px dashed rgb(153, 153, 153); padding: 5px; overflow: auto; font-family: Andale Mono,Lucida Console,Monaco,fixed,monospace; color: rgb(0, 0, 0); background-color: rgb(238, 238, 238); font-size: 12px; line-height: 14px; width: 100%;">

<code>



</code>

</pre>



---
name: hoang nguyen
nickname: mathhoang
Y!M: vietnam_hoangminhnguyen@yahoo.com
mail: vietnam_hoangminhnguyen@Yahoo.com
---