Re: Binder language, binding directories, bind by copy/reference

Instead of renaming it, I'd recommend removing the original code, and
putting in code that sends back an escape message to the caller, telling
it that it's using an obsolete function.

The renaming thing is a good idea, but won't affect any code that's
already been bound to the service program.   If this code is being
distributed to customers/business partners/etc, you don't have the luxury
of re-binding all the programs yourself.

But, sticking that escape message in there will make it quite clear that
you need them to update their code. :)


On Fri, 20 Jun 2003, Brian Parkins wrote:
> >Another question: does anyone have any suggestions for how best to handle
> >the situation where an export in the middle of the list becomes
> >redundant/obsolete and should be deleted (ideally)?
>
> I'd suggest you leave it where it is until such time as you refresh
> (re-bind) those programs and service programs using this particular service
> prgram.
>
> You may wish to rename the obsolete export to avoid any inadvertent use in
> subsequent binds