BinderShell.h

Go to the documentation of this file.

    void EntryCreated(INode who, SString name, IBinder entry);
    
    ...
}
@endcode

Given that, let's write a shell function that handles the same
method signature:

@verbatim
/# function handleEntryCreated() {
    echo "Created: parent=" $1
    echo "Created: name=" $2
    echo "Created: entry=" $3
}
@endverbatim

We can now use the @c link shell command to set up a link from the @c /services
directory to our new shell method.

@verbatim
/# n=$[inspect /services org.openbinder.support.INode]
Result: sptr<IBinder>(0x8091dc4 8BCatalog)

/# link $n $SELF @{EntryCreated->handleEntryCreated}
@endverbatim

This says "make a link from the object @c $n to the object @c $SELF, such that
when @c EntryCreated is pushed from @c $n we will have the @c handleEntryCreated
method called on @c $SELF".  And thus, upon adding a new entry to
@c /services, we will see this:

@verbatim
/# publish /services/test linktest
Publishing: /services/test
/# Created: parent= SValue(sptr<IBinder>(0xb69063f4 8BCatalog))
Created: name= test
Created: entry= SValue(sptr<IBinder>(0x8081254 N18SDatumGeneratorInt12IndexedDatumE))
@endverbatim

Links are a very powerful mechanism, though not the only way to achieve the
same result.  Depending on your needs, you can just as well write your own
notification mechanism for a specialized purpose, or use IInformant for
a more generalized implementation of broadcasting without using links.
A plain link, however, has significant advantages in being clearly documented
in IDL and a standard mechanism that many other things will be able to use
without being written specifically to receive your event.


*/

---

Generated on Wed Dec 28 22:33:27 2005 by Doxygen 1.4.4 for OpenBinder Documentation Version 1.0

PalmSource, Inc. © 2005