Difference between revisions of "Documentation/DevGuide/WritingUNO/Using the UNO Executable"
OOoWikiBot (Talk | contribs) m (Robot: Changing Category:Writing UNO Components) |
OOoWikiBot (Talk | contribs) m (Robot: Automated text replacement (-Category:Documentation/Developers Guide/Professional UNO +Category:Documentation/Developers Guide/Writing UNO)) |
||
| Line 14: | Line 14: | ||
{{PDL1}} | {{PDL1}} | ||
| − | [[Category:Documentation/Developers Guide/ | + | [[Category:Documentation/Developers Guide/Writing UNO]] |
Revision as of 07:26, 4 June 2008
- Standalone Use Case
- Server Use Case
- Using the UNO Executable
The main benefit of using the uno tool as a replacement for writing executables is that the service manager initialization is separated from the task-solving code and the component can be reused. For example, to have multiple XMain implementations run in parallel in one process. There is more involved when writing a component compared to writing an executable. With the bootstrap variable mechanism there is a lot of freedom in bootstrapping the service manager (see chapter C++ Language Binding).
The uno tool is a good starting point when exporting a certain component as a remote server. However, when using the UNO technology later, the tool does have some disadvantages, such as multiple objects can not be exported or the component can only be initialized with command line arguments. If the uno tool becomes insufficient, the listening part in an executable will have to be re-implemented.
| Content on this page is licensed under the Public Documentation License (PDL). |
