Summary: | Subset a minimum POA | ||
---|---|---|---|
Product: | TAO | Reporter: | Jeff Parsons <j.parsons> |
Component: | POA | Assignee: | Johnny Willemsen <jwillemsen> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | ||
Priority: | P3 | ||
Version: | 1.5 | ||
Hardware: | All | ||
OS: | All | ||
Bug Depends on: | 2546 | ||
Bug Blocks: | 2454 |
Description
Jeff Parsons
2006-03-17 12:21:34 CST
Jeff, this will mean that people who need a full blown POA do need to link two libs, is this something we want? Well, it's more like they would be linking to maybe 13 libs instead of 12, most of which are handled under the hood. When I look at it that way, it doesn't seem like much of a change. I think if we have base projects in MPC like full_poa and minimum_poa, and the differences are well-documented, that it won't be painful for app developers. On the other hand, what about the developers who want minimum footprint? Do they have an option now at all? accept using MPC with base projects and recompilation of IDL for a full ORB, CORBA/e compact or CORBA/e micro I don't think we need the seperate the portableserver library anymore closing this as invalid, with mpc we can now generate a much smaller poa library |