GridLab
Grid Application Toolkit

A simple API for Grid Applications
GAT

Menu



next up previous contents
Next: Reading and Writing on Up: The Streaming Package Previous: Advertising Endpoints   Contents

Connecting on Endpoints

Once your friend has placed her phone number in the book, you can call them by simply finding the number in the phone book and letting your fingers do the walking. The same is true of GAT.

Once a process has placed a GATEndpoint in a GATAdvertService, anyone that wants to to ``talk'' to that process simply needs to find that GATEndpoint instance in the GATAdvertService then connect using the retrieved GATEndpoint instance.

As you already know how to retrieve instances from a GATAdvertService, this was covered in Chapter [*], we'll simply skip to the meat of the matter, connection. Upon retrieving a GATEndpoint instance from a GATAdvertService, one can connect to the process that placed the GATEndpoint there by calling the function

GATResult GATEndpoint_Connect( GATEndpoint_const endpoint, GATPipe *peep)

Its first argument is the GATEndpoint retrieved from the GATAdvertService. The second argument is a pointer to a GATPipe, a class which we will cover below. It is through this pointer that the function returns a GATPipe used to communicate with the remote process. Finally this function returns a GATResult, covered in Appendix [*], which indicates this function's completion status.


next up previous contents
Next: Reading and Writing on Up: The Streaming Package Previous: Advertising Endpoints   Contents
Andre Merzky 2004-05-13