Just noticed that my reply never made it to the mailing list. It was
probably my fault. For those still waiting for reply, thinking I was very
rude <g> here it is.
.............
There was a couple of questions came to me personally which I would like to
answer in public.
>If I read your PFC List posting correctly you don`t explicitedly say that
>the approach used by Gary Hyland (see his posting below) and myself won`t
>work, that is having the application specific code below the common
>framework PBDs and avoiding the PFC inheritance loop problem you describe.
>Granted any changes to the common ancestor PBLs then require each descentant
>app to be rebuilt (but this is now a very infrequent process for us) etc etc
>etc. This approach has worked and continues to work very well for us.
>
>I would be interested to hear if you believe this specific approach is
>invalid.
Absolutely correct. I simply wanted to share what I have learned about
PBVM internals and what was relevant to the issue of sharing PBDs across
multiple applications. I cannot say that Gary's or your approach will not
work. And since I have not used it myself, nor can I guarantee that it
will. Hopefully the info I provided will help you to come to your own
conclusions.
>Where did you get this info ?
One of the sources was the conference PM session on PBVM Internals. At
the conference there was a vendor selling audio tapes of all the PM
sessions. I have the contact info somewhere. Let me dig it up...
Boris Gasin
mailto:[EMAIL PROTECTED]
___
____ _
_____ _
____ _
___
Chief Technology Officer
Dynamic Technology Group, Inc.
http://www.dynamictechgroup.com/
1055 Parsippany Blvd., Suite 501-26
Parsippany, NJ 07054
Phone: 973.402.5600
Fax: 973.402.5620
> [EMAIL PROTECTED] HOSTED BY IIGG, INC. FOR HELP WITH LIST SERVE COMMANDS, ADDRESS
> A MESSAGE TO [EMAIL PROTECTED] WITH THE FOLLOWING MESSAGE: help pfcsig
> SEND ALL OTHER INQUIRES TO [EMAIL PROTECTED]
