Поиск по:rtm-cs.sinp.msu.ru -
Поискать по всем серверам
На этой странице приведены все страницы сервера rtm-cs.sinp.msu.ru ,которые мы индексируем. Показаны документы 381 - 400 из 1170.
Упорядочить по:
URL
|
дате изменения
381. Using the CG-editor
... The CG-editor allows the insertion, editing and removal of nodes. The editor supports the following actions on conceptual graph nodes: . left mouse button . ... Edit the contents of conceptual graph node currently pointed at. control + shift + left mouse button . Remove the node (and all its descendents) currently pointed at. right mouse button . ... Selecting an entry from it will add a corresponding subtree to the node currently pointed at. ...
[
Сохраненная копия
]
Ссылки http://rtm-cs.sinp.msu.ru/manual/mico/doc/node71.html -- 4.5 Кб -- 07.06.1999
Похожие документы
Похожие документы
382. LICENSE
Next: GNU Library General Public Up: No Title Previous: Using the CG-editor . This chapter contains the license conditions for MICO. All libraries are covered by the GNU Library General Public License (LGPL) version 2 or later, code generated by the IDL compiler is not copyrighted, everything else is covered by the GNU General Public License (GPL) version 2 or later. ... GNU Library General Public License . GNU General Public License . ...
[
Сохраненная копия
]
Ссылки http://rtm-cs.sinp.msu.ru/manual/mico/doc/node72.html -- 4.0 Кб -- 07.06.1999
Похожие документы
Похожие документы
383. GNU Library General Public License
Next: GNU General Public License Up: LICENSE Previous: LICENSE . ... This License Agreement applies to any software library which contains a notice placed by the copyright holder or other authorized party saying it may be distributed under the terms of this Library General Public License (also called ``this License''). ... You may opt to apply the terms of the ordinary GNU General Public License instead of this License to a given copy of the Library. ... You must supply a copy of this License. ...
[
Сохраненная копия
]
Ссылки http://rtm-cs.sinp.msu.ru/manual/mico/doc/node73.html -- 21.5 Кб -- 07.06.1999
Похожие документы
Похожие документы
384. GNU General Public License
Next: Frequently Asked Questions About Up: LICENSE Previous: GNU Library General Public . ... This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License. ... You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following: . ...
[
Сохраненная копия
]
Ссылки http://rtm-cs.sinp.msu.ru/manual/mico/doc/node74.html -- 16.0 Кб -- 07.06.1999
Похожие документы
Похожие документы
385. Frequently Asked Questions About MICO
... During compilation my gcc 2.7.2.x dies with an "internal compiler error". ... You have to recompile gcc 2.7.2.x, or better yet, install egcs 1.x or gcc 2.8.x. Q: . I have installed gcc 2.8 or egcs, and it still dies with an "internal compiler error". ... You are encouraged to submit a bug report to the appropriate compiler's mailing list. In the meantime, disabling optimization usually works./configure --disable-optimize . ... I configured for namspace support but MICO doesn't compile? ...
[
Сохраненная копия
]
Ссылки http://rtm-cs.sinp.msu.ru/manual/mico/doc/node75.html -- 7.8 Кб -- 07.06.1999
Похожие документы
Похожие документы
386. References
... ISO/IEC 10746-1: Basic Reference Model of Open Distributed Processing Part 1: Overview and Guide to the use of the Reference Model, July 1994. ... ISO/IEC 10746-2: Basic Reference Model of Open Distributed Processing Part 2: Descriptive Model, 1994. ... ISO/IEC 10746-3: Basic Reference Model of Open Distributed Processing Part 3: Prescriptive Model, February 1994. ... ISO/IEC 10746-4: Basic Reference Model of Open Distributed Processing Part 4: Architectural Semantics, 1994. ...
[
Сохраненная копия
]
Ссылки http://rtm-cs.sinp.msu.ru/manual/mico/doc/node76.html -- 4.3 Кб -- 07.06.1999
Похожие документы
Похожие документы
387. BOA Daemon
Next: Implementation Repository Up: BOA Previous: BOA Initialization . The BOA daemon ( micod ) is the part of the basic object adapter that activates object implementations when their service is requested. ... To make all MICO applications use a single implementation repository you have to take similar actions as for the interface repository as described in section 4.2 . ... Specifies the file name where micod should save the contents of the implementation repository when exiting . ...
[
Сохраненная копия
]
Ссылки http://rtm-cs.sinp.msu.ru/manual/mico/doc/node26.html -- 5.1 Кб -- 07.06.1999
Похожие документы
Похожие документы
388. Implementation Repository
... 1: module CORBA { 2: /* 3: * Implementation Repository Entry 4: */ 5: interface ImplementationDef { 6: 7: enum ActivationMode { 8: ActivateShared, ActivateUnshared, 9: ActivatePerMethod, 10: ActivatePersistent, 11: ActivateLibrary 12: }; 13: 14: typedef sequence string RepoIdList; 15: 16: attribute ActivationMode mode ; 17: attribute RepoIdList repoids; 18: readonly attribute string name; 19: attribute string command; 20: }; 21: 22: /* 23: * ... activation mode . ... Listing All Entries ...
[
Сохраненная копия
]
Ссылки http://rtm-cs.sinp.msu.ru/manual/mico/doc/node27.html -- 6.9 Кб -- 07.06.1999
Похожие документы
Похожие документы
389. Listing All Entries
. Next: Details For One Entry Up: Implementation Repository Previous: Implementation Repository . Just issue the following command: . imr list . and you will get a listing of the names of all entries in the implementation repository. Next: Details For One Entry Up: Implementation Repository Previous: Implementation Repository . Arno Puder . Mon Jun 7 10:53:40 PDT 1999
[
Сохраненная копия
]
Ссылки http://rtm-cs.sinp.msu.ru/manual/mico/doc/node28.html -- 3.2 Кб -- 07.06.1999
Похожие документы
Похожие документы
390. Details For One Entry
. Next: Creating New Entries Up: Implementation Repository Previous: Listing All Entries . imr info <name> . will show you detailed information for the entry named <name> . Next: Creating New Entries Up: Implementation Repository Previous: Listing All Entries . Arno Puder . Mon Jun 7 10:53:40 PDT 1999
[
Сохраненная копия
]
Ссылки http://rtm-cs.sinp.msu.ru/manual/mico/doc/node29.html -- 3.1 Кб -- 07.06.1999
Похожие документы
Похожие документы
391. Creating New Entries
Next: Deleting Entries Up: Implementation Repository Previous: Details For One Entry . imr create <name> <mode> <command> <repoid1> <repoid2> ... will create a new entry with name <name> . mode> is one of . ... command> is the shell command that should be used to start the server. ...
[
Сохраненная копия
]
Ссылки http://rtm-cs.sinp.msu.ru/manual/mico/doc/node30.html -- 3.9 Кб -- 07.06.1999
Похожие документы
Похожие документы
392. Deleting Entries
. Next: Forcing Activation of an Up: Implementation Repository Previous: Creating New Entries . imr delete <name> . will delete the entry named <name> . Next: Forcing Activation of an Up: Implementation Repository Previous: Creating New Entries . Arno Puder . Mon Jun 7 10:53:40 PDT 1999
[
Сохраненная копия
]
Ссылки http://rtm-cs.sinp.msu.ru/manual/mico/doc/node31.html -- 3.1 Кб -- 07.06.1999
Похожие документы
Похожие документы
393. Forcing Activation of an Implementation
Next: Examples Up: Implementation Repository Previous: Deleting Entries . Registering an implementation in the implementation repository does not automatically activate the implementation. Usually a non-persistent implementation is only activated by the BOA daemon when its service is requested by a client. But sometimes you have to force activation of an implementation, for instance to make the implementation register itself with a naming service. imr activate <name> [<micod-address>] . ...
[
Сохраненная копия
]
Ссылки http://rtm-cs.sinp.msu.ru/manual/mico/doc/node32.html -- 4.0 Кб -- 07.06.1999
Похожие документы
Похожие документы
394. Examples
Next: Activation Modes Up: Implementation Repository Previous: Forcing Activation of an . Assume we want to register the account server account_server2 from section 3.3.3 as a shared server. ... Recall that this server implemented the interface Account whose repository id is IDL:Account:1.0 . ... imr create Account shared /usr/bin/account_server2 IDL:Account:1.0 . ... imr create Account shared "rsh diamant /usr/bin/account_server2" \ IDL:Account:1.0 . ... account_client2.cc .. ...
[
Сохраненная копия
]
Ссылки http://rtm-cs.sinp.msu.ru/manual/mico/doc/node33.html -- 5.5 Кб -- 07.06.1999
Похожие документы
Похожие документы
395. Activation Modes
Next: Activation Mode Shared Up: BOA Previous: Examples . As mentioned in the previous section the BOA supports several activation modes. Using them is not simply a matter of creating an implementation repository entry, instead an object implementation has to use special BOA functionality according to the selected activation mode. ... Activation Mode Shared . Activation Mode Persistent . Activation Mode Unshared . Activation Mode Per Method . Activation Mode Library . ...
[
Сохраненная копия
]
Ссылки http://rtm-cs.sinp.msu.ru/manual/mico/doc/node34.html -- 3.9 Кб -- 07.06.1999
Похожие документы
Похожие документы
396. Activation Mode Shared
Next: Activation Mode Persistent Up: Activation Modes Previous: Activation Modes . ... 1: // file account _server2.cc 2: 3: #include account .h 4: 5: class Account _impl : virtual public Account _skel 6: { 7: // unchanged, see section MICO Application 8: // ... 9: }; 10: 11: 12: int main( int argc, char *argv[] ) 13: { 14: // ORB initialization 15: CORBA :: ORB _var orb = CORBA :: ORB _init( argc, argv, mico-local- orb ); 16: CORBA :: BOA _var boa = orb - ...
[
Сохраненная копия
]
Ссылки http://rtm-cs.sinp.msu.ru/manual/mico/doc/node35.html -- 6.8 Кб -- 07.06.1999
Похожие документы
Похожие документы
397. Activation Mode Persistent
Next: Activation Mode Unshared Up: Activation Modes Previous: Activation Mode Shared . Persistent servers are just like shared servers, except that the BOA daemon does not activate them. ... The code of a persistent server looks exactly like that of a a shared server. ... However, there is a reason to have even persistent servers register with the BOA daemon: you can do a bind() using the address of the BOA daemon, that is you do not need to know the address of the persistent server. ...
[
Сохраненная копия
]
Ссылки http://rtm-cs.sinp.msu.ru/manual/mico/doc/node36.html -- 4.8 Кб -- 07.06.1999
Похожие документы
Похожие документы
398. Activation Mode Unshared
Next: Activation Mode Per Method Up: Activation Modes Previous: Activation Mode Persistent . ... 1: // file account _server2.cc 2: 3: #include account .h 4: 5: class Account_impl : virtual public Account _skel 6: { 7: // unchanged, see section MICO Application 8: // ... 9: }; 10: 11: 12: int main( int argc, char *argv[] ) 13: { 14: // ORB initialization 15: CORBA :: ORB _var orb = CORBA :: ORB _init( argc, argv, mico-local- orb ); 16: CORBA :: BOA _var boa = orb - ...
[
Сохраненная копия
]
Ссылки http://rtm-cs.sinp.msu.ru/manual/mico/doc/node37.html -- 7.5 Кб -- 07.06.1999
Похожие документы
Похожие документы
399. Activation Mode Per Method
Next: Activation Mode Library Up: Activation Modes Previous: Activation Mode Unshared . Per Method servers are similar to unshared servers, except that a new server instance is launched for each method invocation. The code for a per method server looks the same as for an unshared server. But note that run() will return after the first method invocation, whereas in an unshared server run() will not return until you call shutdown() . ...
[
Сохраненная копия
]
Ссылки http://rtm-cs.sinp.msu.ru/manual/mico/doc/node38.html -- 3.4 Кб -- 07.06.1999
Похожие документы
Похожие документы
400. Activation Mode Library
Next: Making Objects Persistent Up: Activation Modes Previous: Activation Mode Per Method . All activation modes discussed up until now assume client and server are different programs that run in separate processes. ... The function mico_module_exit() is called just before the module is unloaded from the client and should release all allocated resources: in our example the account object created in mico_module_init() . mico_module_exit() is only called if mico_module_init() returned TRUE . ...
[
Сохраненная копия
]
Ссылки http://rtm-cs.sinp.msu.ru/manual/mico/doc/node39.html -- 7.6 Кб -- 07.06.1999
Похожие документы
Похожие документы