Re: Implementating Multithreading or Forking with XMLRPC C server

"amit_basnak25" <[email protected]>
Newsgroups gmane.text.xml.rpc.specification
Message-ID <[email protected]>
Bryan 

Thanks for your inputs.  I will go through the sample files provided 
in the package of xmlrpc -c . 
I have one more question.
How do I pass a C structure request from client to server in xmlrpc-
c ? I understand that xmlrpc-c uses its ow mechanism for passing 
arrays and structures.
Thanks for your time
Regards
Amit   


--- In [email protected], bryanh@... wrote:
>
> >We will be implementing either multithreading or Forking with 
XMLRPC
> >Server.
> >
> >From the sample code files it looks like XMLRPC C uses 
multithreading
> >techniques.  I'm not sure how multithreading is used with XMLRPC C
> >Server. is inclusion of pthread.h is the only way to identify that
> >multithreading is implemented in C?
> >
> >Also is there any way to implement Forking within the same.
> 
> I assume you're talking about the XML-RPC For C/C++, aka Xmlrpc-c, 
package.
> 
> While the package contains facilities to create just about any 
kind of
> server you want, the kind that does the most work for you is the
> free-running Abyss-based server you see in the
> "xmlrpc_sample_add_server" example.  Such a server ordinarily uses
> pthreads -- one thread for each HTTP connection.  But there is an
> alternative version, intended for systems that don't have pthreads,
> that uses fork instead.  You build that with the
> --disable-abyss-threads option to 'configure'.
> 
> -- 
> Bryan Henderson                                    Phone 408-621-
2000
> San Jose, California
>






 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/xml-rpc/

<*> To unsubscribe from this group, send an email to:
    [email protected]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.