• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Multicasti socket network_chat_program_synopsis
 

Multicasti socket network_chat_program_synopsis

on

  • 413 views

 

Statistics

Views

Total Views
413
Views on SlideShare
413
Embed Views
0

Actions

Likes
0
Downloads
0
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft Word

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Multicasti socket network_chat_program_synopsis Multicasti socket network_chat_program_synopsis Document Transcript

    • Multicast Socket Network Chat ProgramMulticast Sockets Chat ProgramUnicasting would be inappropriate for these applications, as for eventsattended by thousands of clients, the load on the server and the networkwould be excessive. Multicasting means that the server only has to sendmessages just once, and they will be distributed to a whole group of clients.Only systems that are members of the group participate in the networktransfers.In the last few chapters, we discussed socket programming using connection-oriented and connection-less protocols. Chapter 6 showed how we can sendbroadcasts with the UDP protocol. In this chapter, the UDP protocol againrears its head, but now we are using multicasts.Multicasts can be used for group communications over the Internet, whereevery node participating in the multicast has to join the group set up for thepurpose. Routers can forward messages to all interested nodes.In this chapter, we will create two Windows applications using multicastingfeatures. With one application it will be possible to chat with multiple systems,where everyone is both a sender and a receiver. The second application – inthe form of a picture show – demonstrates how large data packets can be sentto multiple clients without using a large percentage of the network bandwidth.In particular, we will:  Compare unicasts, broadcasts, and multicasts  Examine the architecture of multicasting  Implement multicast sockets with .NET  Create a multicast chat application  Create a multicast picture show applicationUnicasts, Broadcasts, and MulticastsThe Internet Protocol supports three kinds of IP addresses:  Unicast – unicast network packets are sent to a single destination
    •  Broadcast – broadcast datagrams are sent to all nodes in a subnetwork  Multicast – multicast datagrams are sent to all nodes, possibly on different subnets, that belong to a groupThe TCP protocol provides a connection-oriented communication where twosystems communicate with each other; with this protocol, we can only sendunicast messages. If multiple clients connect to a single server, all clientsmaintain a separate connection on the server. The server needs resources foreach of these simultaneous connections, and must communicate individuallywith every client. Dont forget that the UDP protocol can also be used to sendunicast messages, where, unlike TCP, connection-less communication is used,making it is faster than TCP, although without TCPs reliability..Broadcast addresses are identified by IP addresses where all bits of the hostare set to 1. For instance, to send messages to all hosts in a subnet with amask of 255.255.255.0 in a network with the address 192.168.0, thebroadcast address would be 192.168.0.255. Any host with an IP addressbeginning 192.168.0 will then receive the broadcast messages. Broadcastsare always performed with connection-less communication using the UDPprotocol. The server sends the data regardless of whether any client islistening. Performance reasons mean it wouldnt be possible to set up aseparate connection to every client. Connection-less communication meansthat the server does not have to allocate resources for every single client – nomatter how many clients are listening, the same server resources will beconsumed.Of course, there are disadvantages to the connection-less mechanism. Forone, there is no guarantee that the data is received by anyone. If we wantedto add reliability, we would have to add a handshaking mechanism of our ownat a higher level than UDP.
    • Hardware RequirementsProcessor : Pentium IV 2GHz and AboveRAM : 2GB RAMMonitor : 15” Color MonitorKeyboardMouseSoftware RequirementsOperating System. : Windows XPDeveloping Tool : C#Database : MS Access/SQL Server