your code is only reading one line (as in stops at a \n), but my data that's being sent, can include more than 0 \n's, could that be causing the problem?
You could use something else to mean end-of-message, how about a carriage return, '\r'?
Quote:
maybe somewhere (not at the end) in the data i send, there is a \0...?
I don't think so. You could compare how many bytes you read() against how many bytes str_len sees, if they disagree a lot there's a NULL or newline in the middle.
Wait! That's it! Your str_len function stops at a newline and some of your messages have a newline in the middle!
You still need to divide it into records somehow though. The code can't be relied on if you don't.
Hi !
I had a verry simple question to ask...
In unix when we create pipes.. the unnamed pipes that is...
is there any way to access those pipes outside the code ?
Another thing.. do sockets have an entry in the inode table ?
TIA,
Devyani. (1 Reply)
I am looking for a way to have a program listen on a port (example: 8000) for communication I will be sending via that port to it(Linux Kernel machine). Once it recieves an appropiate command I need it to run a .bat file in linux.
I know what I need to do but I am running into a few problems:... (8 Replies)
Hai,
How cani declare socket and collect the data in a string varialbe.
Since i am new to this i am asking this.
Can we connect multiple port.
Thank you. (6 Replies)
Is there a way to see what sockets are in use? The developers here are getting some defunct processes and they would like to get a socket list.
This is on a Solaris 8 machine.
Thanks! (1 Reply)
Is it possible to trace the packages and the statuses of client's and/or server's sockets by the UNIX network administrative tools?
Two applications interact via sockets. There is no problem if they stay in the same network segment. If their hosts connected through the firewall then they aren't... (4 Replies)
anyone and teach me how to save standard output to a file in a client/server socket. I know how to read them to the screen but i'm not quite sure how to save them to a file.
my read to screen file code:
memset(line, 0x0, LINE_ARRAY_SIZE);
while (recv(connectSocket, line, MAX_MSG, 0) >... (1 Reply)
Hi,i now moved into a different section where i need to use sockets.
i am completely nill in sockets.
can some body please provide me what are the requirements for a socket.
to use sockets in c.
thanks (1 Reply)
hai guys,
I'm doing a project in which one server communicates with several clients. How can i do it when i have different port numbers???:confused: (0 Replies)
Hi, i am student, think learning about c++, someone has a example the how establish a conection with sockets :b::b: (1 Reply)
Discussion started by: mmartinez
1 Replies
LEARN ABOUT CENTOS
ldns_wire2rdf
ldns(3) Library Functions Manual ldns(3)NAME
ldns_wire2rr, ldns_wire2pkt, ldns_wire2rdf, ldns_wire2dname
SYNOPSIS
#include <stdint.h>
#include <stdbool.h>
#include <ldns/ldns.h>
ldns_status ldns_wire2rr(ldns_rr **rr, const uint8_t *wire, size_t max, size_t *pos, ldns_pkt_section section);
ldns_status ldns_wire2pkt(ldns_pkt **packet, const uint8_t *data, size_t len);
ldns_status ldns_wire2rdf(ldns_rr *rr, const uint8_t *wire, size_t max, size_t *pos);
ldns_status ldns_wire2dname(ldns_rdf **dname, const uint8_t *wire, size_t max, size_t *pos);
DESCRIPTION
ldns_wire2rr() converts the data on the uint8_t bytearray (in wire format) to a DNS resource record. This function will initialize and
allocate memory space for the rr structure. The length of the wiredata of this rr is added to the *pos value.
rr: pointer to the structure to hold the rdata value
wire: pointer to the buffer with the data
max: the length of the data buffer (in bytes)
pos: the position of the rr in the buffer (ie. the number of bytes from the start of the buffer)
section: the section in the packet the rr is meant for
Returns LDNS_STATUS_OK if everything succeeds, error otherwise
ldns_wire2pkt() converts the data on the uint8_t bytearray (in wire format) to a DNS packet. This function will initialize and allocate
memory space for the packet structure.
packet: pointer to the structure to hold the packet
data: pointer to the buffer with the data
len: the length of the data buffer (in bytes)
Returns LDNS_STATUS_OK if everything succeeds, error otherwise
ldns_wire2rdf() converts the data on the uint8_t bytearray (in wire format) to DNS rdata fields, and adds them to the list of rdfs of the
given rr. This function will initialize and allocate memory space for the dname structures. The length of the wiredata of these
rdfs is added to the *pos value.
All rdfs belonging to the RR are read; the rr should have no rdfs yet. An error is returned if the format cannot be parsed.
rr: pointer to the ldns_rr structure to hold the rdata value
wire: pointer to the buffer with the data
max: the length of the data buffer (in bytes)
pos: the position of the rdf in the buffer (ie. the number of bytes from the start of the buffer)
Returns LDNS_STATUS_OK if everything succeeds, error otherwise
ldns_wire2dname() converts the data on the uint8_t bytearray (in wire format) to a DNS dname rdata field. This function will initialize and
allocate memory space for the dname structure. The length of the wiredata of this rdf is added to the *pos value.
dname: pointer to the structure to hold the rdata value
wire: pointer to the buffer with the data
max: the length of the data buffer (in bytes)
pos: the position of the rdf in the buffer (ie. the number of bytes from the start of the buffer)
Returns LDNS_STATUS_OK if everything succeeds, error otherwise
AUTHOR
The ldns team at NLnet Labs. Which consists out of Jelte Jansen and Miek Gieben.
REPORTING BUGS
Please report bugs to ldns-team@nlnetlabs.nl or in our bugzilla at http://www.nlnetlabs.nl/bugs/index.html
COPYRIGHT
Copyright (c) 2004 - 2006 NLnet Labs.
Licensed under the BSD License. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
SEE ALSO
ldns_rr2wire, ldns_pkt2wire, ldns_rdf2wire, ldns_dname2wire. And perldoc Net::DNS, RFC1034, RFC1035, RFC4033, RFC4034 and RFC4035.
REMARKS
This manpage was automaticly generated from the ldns source code by use of Doxygen and some perl.
30 May 2006 ldns(3)