Serialization of a char buffer Post: 302712655

8 More Discussions You Might Find Interesting

1. Programming

How to achieve Serialization in Unix C, C++

How to achieve SERIALIZATION in Unix , C, C++ Write Objects directly to disk and read back ?

2. Shell Programming and Scripting

How to replace any char with newline char.

Hi, How to replace any character in a file with a newline character using sed .. Ex: To replace ',' with newline Input: abcd,efgh,ijkl,mnop Output: abcd efgh ijkl mnop Thnx in advance. Regards, Sasidhar

3. Programming

Adding a single char to a char pointer.

Hello, I'm trying to write a method which will return the extension of a file given the file's name, e.g. test.txt should return txt. I'm using C so am limited to char pointers and arrays. Here is the code as I have it: char* getext(char *file) { char *extension; int i, j;...

4. Programming

concat const char * with char *

hello everybody! i have aproblem! i dont know how to concatenate const char* with char const char *buffer; char *b; sprintf(b,"result.txt"); strcat(buffer,b); thanx in advance

5. Shell Programming and Scripting

how first char in odd line and second char in even line

Hi I m having ifconfig -a o/p like sbanlab1:ksh# ifconfig -a | egrep "flags|inet" | awk -F' ' '{print $1,$2}' lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> inet 127.0.0.1 lo0:1: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> inet 127.0.0.1 bge0:...

6. Programming

error: invalid conversion from �const char� to �char�

Compiling xpp (The X Printing Panel) on SL6 (RHEL6 essentially): xpp.cxx: In constructor ‘printFiles::printFiles(int, char**, int&)’: xpp.cxx:200: error: invalid conversion from ‘const char*’ to ‘char*’ The same error with all c++ constructors - gcc 4.4.4. If anyone can throw any light on...

7. Programming

Special char in a buffer

Hello, Please ,how can verify, if a case of buffer contains a special char ? (in C) Thank you.

8. Programming

Invalid conversion from char* to char

Pointers are seeming to get the best of me and I get that error in my program. Here is the code #include <stdio.h> #include <stdlib.h> #include <string.h> #define REPORTHEADING1 " Employee Pay Hours Gross Tax Net\n" #define REPORTHEADING2 " Name ...

LEARN ABOUT DEBIAN

sasl_client_start

sasl_client_start(3)						  SASL man pages					      sasl_client_start(3)

NAME

       sasl_client_start - Begin an authentication negotiation

SYNOPSIS

       #include <sasl/sasl.h>

       int sasl_client_start(sasl_conn_t * conn,
		       const char * mechlist,
		       sasl_interact_t ** prompt_need,
		       const char ** clientout,
		       unsigned * clientoutlen,
		       const char ** mech);

DESCRIPTION

       sasl_client_start()  selects  a	mechanism for authentication and starts the authentication session. The mechlist is the list of mechanisms
       the client might like to use. The mechanisms in the list are not necessarily supported by the client or even valid. SASL  determines  which
       of  these to use based upon the security preferences specified earlier. The list of mechanisms is typically a list of mechanisms the server
       supports acquired from a capability request.

       If SASL_INTERACT is returned the library needs some values to be filled in before it can proceed. The prompt_need structure will be  filled
       in with requests. The application should fulfill these requests and call sasl_client_start again with identical parameters (the prompt_need
       parameter will be the same pointer as before but filled in by the application).

       mechlist is a list of mechanisms the server has available. Punctuation is ignored.

       prompt_need is filled in with a list of prompts needed to continue (if necessary).

       clientout and clientoutlen is created. It is the initial client response to send to the server. It is the job of the client to send it over
       the network to the server.  Any protocol specific encoding (such as base64 encoding) necessary needs to be done by the client.

       If the protocol lacks client-send-first capability, then set clientout to NULL.

       If there is no initial client-send, then *clientout will be set to NULL on return.

       mech contains the name of the chosen SASL mechanism (on success)

RETURN VALUE

       sasl_client_start  returns  an  integer which corresponds to one of the following codes. SASL_CONTINUE indicates success and that there are
       more steps needed in the authentication. All other return codes indicate errors and should either be handled or the authentication  session
       should be quit.

CONFORMING TO

       RFC 4422

SEE ALSO

       sasl(3), sasl_callbacks(3), sasl_errors(3), sasl_client_init(3), sasl_client_new(3), sasl_client_step(3)

SASL
								   10 July 2001 					      sasl_client_start(3)