User talk:Sajidur89

 Hello and Welcome to Wikiversity Sajidur89! You can contact us with questions at the colloquium or me personally when you need help. Please remember to sign and date your finished comments when participating in discussions. The signature icon above the edit window makes it simple. All users are expected to abide by our Privacy, Civility, and the Terms of Use policies while at Wikiversity.

To get started, you may


 * Take a guided tour and learn to edit.
 * Visit a (kind of) random project.
 * Browse Wikiversity, or visit a portal corresponding to your educational level: pre-school, primary, secondary, tertiary, non-formal education.
 * Find out about research activities on Wikiversity.
 * Explore Wikiversity with the links to your left.


 * Read an introduction for teachers and find out how to write an educational resource for Wikiversity.
 * Give feedback about your initial observations
 * Discuss Wikiversity issues or ask questions at the colloquium.
 * Chat with other Wikiversitans on #wikiversity-en.
 * Follow Wikiversity on twitter (http://twitter.com/Wikiversity) and identi.ca (http://identi.ca/group/wikiversity).

You do not need to be an educator to edit. You only need to be bold to contribute and to experiment with the sandbox or your userpage. See you around Wikiversity! --goldenburg111 (talk) 22:24, 1 December 2013 (UTC)

Review from Jane Kruhinina
After reading the chapter about the TCP I have got a new thoughts and answers in this field. The given information is represented in nice way for understanding and in a friendly for a reader manner. Asking questions and immediately answering them or given the hints for getting the idea is an excellent way to make reader think and remember the piece of information. There are also good examples that are represented while explanation is given along with the images. They play important role as the visualization of what you read makes the information engrave on your memory. But there are some things in this article that I’d recommend to change and correct whether it’s necessary. First thing is the misspelling. It’s okey – we are all people here, so I will just release you from your duties to check the text. - Overview – 4 line-“congested the channel be”(may be “is” instead of “be”) - The TCP segment Header – 2 line - “we will dig deeper into the protocol understand how TCP provides”(missing conjunction). In this section there are some problems with formatting text near the picture. In this part there is also “ I set to 1 to indicate that the URGENT POINTER” sentence which is to be checked. - TCP Segment – 4 line – “ Seond one comes from te Link Layer.” – maybe it’s better to omit “one” or to change the sentence. - Sequence Numbers – 1 line – “So far we have heard about sequence number several times.” – double phrase. It’s my opinion, but may be it has sense to put the TCP segment before TCP segment header, and in its order, to put Sequence Numbers after TCP segment header. Then it looks more logically organized.

As the recommendation to the writing of this chapter we were told to define the Learning objectives of this paper. You do not have them as well as conclusion.

While telling about the fields of TCP header you didn’t mention 2 flags: Along with this I think it would be useful to include clearer and wider description of options for checksum.
 * PSH - means that the receiving TCP stack must immediately inform the application of the arrived data, rather than wait until the buffer is full;
 * RST - is used to cancel connection: because application error, rejection of the wrong segment, attempts to create a connection in the absence of the requested service;

You have described the scheme of how the packets are transferred, but I didn’t notice the way how those packets are created. TCP divides the information you want to send into multiple parts. It numbers each part to restore an order later than. To send this enumeration along with the data it wraps every piece of information with an envelope, which contains relevant information. This is the TCP-envelope. The resulting TCP-package is placed in a separate IP-envelope and we get IP-packet which can already be handled be the network. Recipient (TCP-module (process)) upon receipt unpacks IP-envelopes and sees TCP-envelopes, unpacks them and puts the data into a sequence of parts in the appropriate place. If something is missing, it needs to send this part again. After all information is collected in right order and fully restored. Now the array is sent up to the user (to disk, on the screen, for printing).

Other information about all the processes is clear for me and well described. May be you will find interesting to add information about where and how is the TCP organized in the operation system space but its only my opinion.

All above are my recommendations to TCP chapter and I hope they will be helpful and useful for you.

User:Sajid
Hi! You (perhaps accidentally) created a user page at User:Sajid. Users should only be editing their own user pages, or user pages on other projects they have been invited to. There is a request to delete the User:Sajid page. Rather than deleting this page, I'd like to move it, or at least the content, under your account. Where would you like the content to go? -- Dave Braunschweig (discuss • contribs) 03:25, 22 January 2014 (UTC)


 * Page moved to User:Sajidur89/Web Science. -- Dave Braunschweig (discuss • contribs) 02:02, 24 January 2014 (UTC)