Has anyone given thought to a publish-subscribe model? Something like a
LinkMaster. If you wanted to publish some (or all) information, you would
make a request to the LinkMaster. It would return you a chunk of memory to
fill with your information and you would return it. If you wanted to link,
you could query the LinkMaster for all available links and get a list of
info. If LinkMaster was deleted by the user.. all links, of course, would be
now dead but at least all memory would be freed so no dangling chunks. The
LinkMaster could even age requests for publishing so that if it sent a
chunck of memory but didn't get a response back within a certain amount of
time, it would automatically free the memory.
Just my off the wall thoughts as I was reading this very interesting thread.
--Alan
Alan Johnson
Handsbreadth Inc.
> This would make things more seamless for the user, but it raises a lot of
> development issues. First and foremost, it means that adding
> 'linkability' is a
> much more complicated task. Linking has to be simple enough that
> a sufficiently
> large number of apps will implement it, or else it is of little
> value. This idea
> could require changes to the UI of the program. If it is implemented as a
> sub-launch, then the second app would have much less memory than
> usual, which is
> quite likely to cause problems. If it is not implemented as a
> sub-launch, then
> the id of the calling app must be stored somewhere so the second
> app can return to
> it. The calling app would also have to save additional state so
> that it can
> process the link.
>
> Ben
>
>
>
