Re: socket()
From: Dave (noone_at_nowhere.com)
Date: 02/27/05
- Next message: Dave: "Re: socket()"
- Previous message: Javier J: "Deny _WRITE_ access to a file"
- In reply to: visu: "socket()"
- Next in thread: Dave: "Re: socket()"
- Reply: Dave: "Re: socket()"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Sun, 27 Feb 2005 13:05:31 -0000
just because thats the way it is. if you don't like it you can write your
own functions to combine them into one step if you like.
"visu" <shanker_bejjanki@persistent.co.in> wrote in message
news:ulvUFcKHFHA.3376@TK2MSFTNGP14.phx.gbl...
> Hi
>
>
>
> When we create socket for server , first we use SOCKET () then we will
Bind
> () to the port .
>
> what is the use of this kind of mechanism .
>
>
>
> If u compare this with file opening . why not fopen() used then it will
> Bind() with file name ..?
>
> we use only one statement to open file , But why we use two statement to
> open socket connection..
>
> (why can't we provide port , server structure in socket.) .
>
>
>
> why they designed like that ...?
>
>
>
> Please clear me..
>
>
>
> Thanks
>
> Shanker Bejjanki
>
>
- Next message: Dave: "Re: socket()"
- Previous message: Javier J: "Deny _WRITE_ access to a file"
- In reply to: visu: "socket()"
- Next in thread: Dave: "Re: socket()"
- Reply: Dave: "Re: socket()"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|
