Hi
Przemysław Czerpak wrote:
>
> Client side functions:
> ======================
> NETIO_CONNECT( [<cServer>], [<cPort>], [<nTimeOut>], ;
> [<cPasswd>], [<nCompressionLevel>], [<nStrategy>] )
> -> <lConnected>
> NETIO_DISCONNECT( [<cServer>], [<cPort>] ) -> <lOK>
> NETIO_PROCEXISTS( <cProcName> ) -> <lExists>
> NETIO_PROCEXEC( <cProcName> [, <params,...>] ) -> <lSent>
> NETIO_PROCEXECW( <cProcName> [, <params,...>] ) -> <lExecuted>
> NETIO_FUNCEXEC( <cFuncName> [, <params,...>] ) -> <xFuncRetVal>
>
> Server side functions:
> ======================
> NETIO_LISTEN( [<nPort>], [<cIfAddr>], [<cRootDir>], [<lRPC>] )
> -> <pListenSocket> | NIL
> NETIO_ACCEPT( <pListenSocket>, [<nTimeOut>],
> [<cPass>], [<nCompressionLevel>], [<nStrategy>] )
> -> <pConnectionSocket> | NIL
> NETIO_COMPRESS( <pConnectionSocket>,
> [<cPass>], [<nCompressionLevel>], [<nStrategy>] ) ->
> NIL
> NETIO_SERVER( <pConnectionSocket> ) -> NIL
> NETIO_RPC( <pListenSocket> | <pConnectionSocket> [, <lEnable>] ) ->
> <lPrev>
> NETIO_RPCFILTER( <pConnectionSocket>,
> <sFuncSym> | <hValue> | NIL ) -> NIL
> NETIO_SERVERSTOP( <pListenSocket> | <pConnectionSocket> [, <lStop>] )
> -> NIL
> NETIO_MTSERVER( [<nPort>], [<cIfAddr>], [<cRootDir>],
> [<lRPC> | <sFuncSym> | <hValue>],
> [<cPasswd>], [<nCompressionLevel>], [<nStrategy>] )
> -> <pListenSocket>
>
Is not it appropriate to distinguish functions by server/client side as :
NETIO_C_CONNECT( [<cServer>], [<cPort>], [<nTimeOut>], ;
[<cPasswd>], [<nCompressionLevel>], [<nStrategy>] )
-> <lConnected>
NETIO_C_DISCONNECT( [<cServer>], [<cPort>] ) -> <lOK>
...
NETIO_S_LISTEN( [<nPort>], [<cIfAddr>], [<cRootDir>], [<lRPC>] )
-> <pListenSocket> | NIL
NETIO_S_ACCEPT( <pListenSocket>, [<nTimeOut>],
[<cPass>], [<nCompressionLevel>], [<nStrategy>] )
-> <pConnectionSocket> | NIL
So that user always know what he is intended to do.
I mean s sort of distinction by function name, my opinion only.
Regards
Pritpal Bedi
--
View this message in context:
http://old.nabble.com/hbnetio---rpc-filter-tp27133404p27146610.html
Sent from the Harbour - Dev mailing list archive at Nabble.com.
_______________________________________________
Harbour mailing list (attachment size limit: 40KB)
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
