Subject | Re: INET/inet_error: read errno |
---|---|
Author | Ali Gökçen |
Post date | 2005-10-26T08:01:53Z |
Hi Ann,
using in HEX format at user level.
so there is no ASCII NULL(0x0) posibility, because of we display
it as char '0' (decimal 48)
if all bytes were be zero, we will keep it as string '000000000000'
if all bytes were be one, we will keep it as string 'FFFFFFFFFFFF'.
There is no risc here about byte level declerations i think.
Am i missing something?
Regards.
Ali
P.S. To Adam: client computers may close their ethernet connection
when they are going into suspend mode. So, FB server can not
communicate with them with the same connection session.
Take a look to your clients, if they are going to a coffe break or
meeting or lobby chat, when you applications and transactions opened.
> Ali Gökçen wrote:If i know it correctly, NIC numbers are 6 byte identifier and
> >
> > MAC_ID CHAR(12) CHARACTER SET OCTETS. -- or none
> >
>
> Use OCTETs - zeros confuse code that's expecting
> charset none, and under some circumstances, charset
> none is padded with spaces (0x20?) rather than 0x0.
>
> Cheers,
>
> Ann
using in HEX format at user level.
so there is no ASCII NULL(0x0) posibility, because of we display
it as char '0' (decimal 48)
if all bytes were be zero, we will keep it as string '000000000000'
if all bytes were be one, we will keep it as string 'FFFFFFFFFFFF'.
There is no risc here about byte level declerations i think.
Am i missing something?
Regards.
Ali
P.S. To Adam: client computers may close their ethernet connection
when they are going into suspend mode. So, FB server can not
communicate with them with the same connection session.
Take a look to your clients, if they are going to a coffe break or
meeting or lobby chat, when you applications and transactions opened.