Charm++ parallel programming system

[Eric Bohm <ebohm AT uiuc.edu>]

1. The client is not written in converse.  It is a sequential C++ 
program which uses the ccs-client API.  It is compiled using g++ (or any 
C++ compiler) not charmc, includes the ccs-client.h header and links to 
the ccs-client library.

Were it an actual converse program it would look quite different.  
Examples of converse programs can be obtained by checking out the pgms/ 
module from our repository.

cd charm;
cvs 
-d:pserver:checkout AT charm.cs.uiuc.edu:/cvsroot
 login;
cvs 
-d:pserver:checkout AT charm.cs.uiuc.edu:/cvsroot
 co pgms/converse;

That directory contains many examples, including an older ccstest which 
is C instead of C++, and megacon, which tests a variety of converse 
features.

There are several existing advanced examples of CCS clients, two use the 
LiveViz library.

Salsa is a java based code to interact with a running cosmology simulation:
http://librarian.phys.washington.edu/astro/index.php/Research:Salsa
lvClient is a sample java liveViz client charm/java/bin/lvClient

If you wish to avoid using the ccs-client code you will need to 
re-implement the API yourself.

2. The converse layer allocates a buffer to store the incoming message 
and its header on the heap. The handler is responsible for CmiFree'ing 
the passed-in message.

Naresh_Hanumanthakari wrote:
> hello,
>  
>     Kindly help for the followings:
>  
>        1. We have already gone through the client.C and server.C in charm/examples/converse/ccstest. The client is also implemented in converse.
>         What i want is the client written in any language other than 
> converse. We might not have CcsConnect, CcsSendRequest and CcsRecvResponse
>         in the client side. Still the client should be able to communicate to 
> the server properly.
>   
>        2. In the server we can have statements like
>  
>               char *DataRecvd;
>               DataRecvd=msg+CmiMsgHeaderSizeBytes;
>  
>         After this DataRecvd contains the data sent from the client side.
>  
>        Could you explain this phenomenon from storage point of view, i.e where the message sent from client is placed. What is i want to know is the working of "msg".
>             
>
>
> DISCLAIMER:
> This email (including any attachments) is intended for the sole use of the 
> intended recipient/s and may contain material that is CONFIDENTIAL AND 
> PRIVATE COMPANY INFORMATION. Any review or reliance by others or copying or 
> distribution or forwarding of any or all of the contents in this message is 
> STRICTLY PROHIBITED. If you are not the intended recipient, please contact 
> the sender by email and delete all copies; your cooperation in this regard is 
> appreciated.
> _______________________________________________
> charm mailing list
> charm AT cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/charm
>