Problem:
- Product Name: VBE
- product Version: 5.x
- Product Component: Notification Service, VisiNotify
- Platform: NA
- Compiler Version: NA
VBE 5.x - libcosnotify versus user-generated CosNotify stubs and skeletons
Resolution:
- What are the implications/side-effects of using user-generated CosNotify stubs and skeletons (saying, by generating them from CosNotify IDL files in ${VBROKER}/examples/vbroker/notify/cos_dir), as opposed to use CosNotify stubs and skeletons in libcosnotify.a?
ANS: libconsnotify.a is simply an archive of compiled generated code. These is nothing additional compared to user generated code. libconsnotify.a does NOT contain any code NOT generated from IDLs. Providing libcosnotify.a is only for users' convenience. Therefore, this is zero impact on using either libcosnotify.a or user generated code. - Does libcosnotify.a contain any functionality in additional to the pure stubs/skeletons generated from scratch? For instance, is Event Batching implemented in that library?
ANS: No. In fact, Event Batching is not implemented inside libcosnotify.a at all, but inside ORB runtime and VisiNotifyServer itself. Therefore, using user generated code will NOT prevent application from using Event Batch feature.
Old KB# 26679
#VisiNotify
#Security
#VisiBroker