Registry-Free COM Registration

本文介绍了Registry-Free COM(Reg-Free COM)的概念及其实现原理。通过将COM组件数据写入应用程序清单文件而非注册表,简化了部署流程并降低了权限需求。此外,文章还探讨了Reg-Free COM的优势与局限性。

Registry-Free COM Registration

InstallShield 2008

With Reg-Free COM, COM data is written to an application manifest file that is stored in the application folder. The manifest file is an XML file that contains information about an application and the libraries that are associated with it. Note that the Reg-Free COM manifest file, the executable file, and the COM libraries should all be installed to the same folder on the target machine.

Benefits of Reg-Free COM

Reg-Free COM has several advantages over traditional COM. For example, with Reg-Free COM, the component is defined within the scope of the application itself. Even if other applications that use the same COM component or a different version of it require that it be registered, it will not interfere with this application.

Problems may occur with traditional COM registration if multiple versions of shared libraries exist on a target system. For example, an installation may overwrite a new version of a shared library with an older version, or a new version might not be backwardly compatible with older versions. This may cause applications that require features of a specific version to crash. These types of situations are commonly known as DLL Hell. With Reg-Free COM, you can avoid these problems because other applications cannot access your application’s COM component.

In addition, Reg-Free COM streamlines the upgrade and uninstallation processes. For an upgrade, simply replace the application folder. For an uninstallation, simply remove that folder.

[[[

Registry-free COM is a method for deploying COM components such that they do not need to be registered on the target machine. This has two main benefits for OpenViz Particles application deployment:

  1. Simplified deployment. Applications can now be deployed simply by copying a folder of files to the machine. MSI, batch or manual registering of the COM dlls is not needed.
  2. Reduced permissions. Because the registry is not touched, applications can be installed by a user without adminstrator or power user permissions. This has long been a problem with COM-based applications, as well as OpenViz Particles .NET applications which depend on the COM dlls.

Registry-free COM may also be referred to by the terms "Isolated Application", "Side-by-Side Assemblies" or "SxS".

Limitations of Reg-Free COM

Reg-Free COM is not appropriate for some solutions. Several limitations exist:

Reg-Free COM works on only Windows XP or later.
A component is not suitable for Reg-Free COM if it is a system component or part of the operating system. In addition, it is not suitable if it is a data access component such as Microsoft Data Access Components (MDAC). These types of components should not be isolated. Some of these components, such as MDAC, can be included in an installation as a redistributable.
A COM component can be isolated only once per application. Consider grouping COM components in a single class library as a workaround to this limitation.

转载于:https://www.cnblogs.com/taoxu0903/archive/2009/10/12/1581685.html

运行rabbitmq日志2025-07-30 08:44:54.598 [debug] <0.287.0> Lager installed handler {lager_file_backend, "d:/Downloads/RabbitMQData/log/rabbit@LAPTOP-FU2L4D12.log"} into lager_event 2025-07-30 08:44:54.598 [debug] <0.290.0> Lager installed handler error_logger_lager_h into error_logger 2025-07-30 08:44:54.608 [debug] <0.293.0> Lager installed handler lager_forwarder_backend into error_logger_lager_event 2025-07-30 08:44:54.608 [debug] <0.296.0> Lager installed handler lager_forwarder_backend into rabbit_log_lager_event 2025-07-30 08:44:54.608 [debug] <0.299.0> Lager installed handler lager_forwarder_backend into rabbit_log_channel_lager_event 2025-07-30 08:44:54.608 [debug] <0.302.0> Lager installed handler lager_forwarder_backend into rabbit_log_connection_lager_event 2025-07-30 08:44:54.608 [debug] <0.305.0> Lager installed handler lager_forwarder_backend into rabbit_log_feature_flags_lager_event 2025-07-30 08:44:54.608 [debug] <0.308.0> Lager installed handler lager_forwarder_backend into rabbit_log_federation_lager_event 2025-07-30 08:44:54.608 [debug] <0.311.0> Lager installed handler lager_forwarder_backend into rabbit_log_ldap_lager_event 2025-07-30 08:44:54.608 [debug] <0.317.0> Lager installed handler lager_forwarder_backend into rabbit_log_prelaunch_lager_event 2025-07-30 08:44:54.608 [debug] <0.314.0> Lager installed handler lager_forwarder_backend into rabbit_log_mirroring_lager_event 2025-07-30 08:44:54.608 [debug] <0.320.0> Lager installed handler lager_forwarder_backend into rabbit_log_queue_lager_event 2025-07-30 08:44:54.608 [debug] <0.323.0> Lager installed handler lager_forwarder_backend into rabbit_log_ra_lager_event 2025-07-30 08:44:54.608 [debug] <0.326.0> Lager installed handler lager_forwarder_backend into rabbit_log_shovel_lager_event 2025-07-30 08:44:54.608 [debug] <0.329.0> Lager installed handler {lager_file_backend, "d:/Downloads/RabbitMQData/log/rabbit@LAPTOP-FU2L4D12_upgrade.log"} into rabbit_log_upgrade_lager_event 2025-07-30 08:44:54.619 [info] <0.44.0> Application lager started on node 'rabbit@LAPTOP-FU2L4D12' 2025-07-30 08:44:54.633 [info] <0.273.0> Log file opened with Lager 2025-07-30 08:44:54.996 [info] <0.44.0> Application mnesia started on node 'rabbit@LAPTOP-FU2L4D12' 2025-07-30 08:44:54.998 [info] <0.273.0> Starting RabbitMQ 3.8.8 on Erlang 23.3.4.18 Copyright (c) 2007-2020 VMware, Inc. or its affiliates. Licensed under the MPL 2.0. Website: https://rabbitmq.com 2025-07-30 08:44:54.998 [info] <0.273.0> node : rabbit@LAPTOP-FU2L4D12 home dir : C:\Users\小橙 config file(s) : (none) cookie hash : mkQxrMfpOoR5L3HCS5ZoGA== log(s) : d:/Downloads/RabbitMQData/log/rabbit@LAPTOP-FU2L4D12.log : d:/Downloads/RabbitMQData/log/rabbit@LAPTOP-FU2L4D12_upgrade.log database dir : d:/Downloads/RabbitMQData/db/rabbit@LAPTOP-FU2L4D12-mnesia 2025-07-30 08:44:55.053 [debug] <0.285.0> Lager installed handler lager_backend_throttle into lager_event 2025-07-30 08:44:59.279 [info] <0.273.0> Running boot step pre_boot defined by app rabbit 2025-07-30 08:44:59.279 [info] <0.273.0> Running boot step rabbit_core_metrics defined by app rabbit 2025-07-30 08:44:59.279 [info] <0.273.0> Running boot step rabbit_alarm defined by app rabbit 2025-07-30 08:44:59.281 [info] <0.361.0> Memory high watermark set to 6473 MiB (6787769958 bytes) of 16183 MiB (16969424896 bytes) total 2025-07-30 08:44:59.480 [info] <0.363.0> Enabling free disk space monitoring 2025-07-30 08:44:59.480 [info] <0.363.0> Disk free limit set to 50MB 2025-07-30 08:44:59.524 [info] <0.273.0> Running boot step code_server_cache defined by app rabbit 2025-07-30 08:44:59.524 [info] <0.273.0> Running boot step file_handle_cache defined by app rabbit 2025-07-30 08:44:59.524 [info] <0.366.0> Limiting to approx 65439 file handles (58893 sockets) 2025-07-30 08:44:59.524 [info] <0.367.0> FHC read buffering: OFF 2025-07-30 08:44:59.524 [info] <0.367.0> FHC write buffering: ON 2025-07-30 08:44:59.525 [info] <0.273.0> Running boot step worker_pool defined by app rabbit 2025-07-30 08:44:59.525 [info] <0.351.0> Will use 8 processes for default worker pool 2025-07-30 08:44:59.525 [info] <0.351.0> Starting worker pool 'worker_pool' with 8 processes in it 2025-07-30 08:44:59.525 [info] <0.273.0> Running boot step database defined by app rabbit 2025-07-30 08:44:59.526 [info] <0.273.0> Node database directory at d:/Downloads/RabbitMQData/db/rabbit@LAPTOP-FU2L4D12-mnesia is empty. Assuming we need to join an existing cluster or initialise from scratch... 2025-07-30 08:44:59.526 [info] <0.273.0> Configured peer discovery backend: rabbit_peer_discovery_classic_config 2025-07-30 08:44:59.526 [info] <0.273.0> Will try to lock with peer discovery backend rabbit_peer_discovery_classic_config 2025-07-30 08:44:59.526 [info] <0.273.0> Peer discovery backend does not support locking, falling back to randomized delay 2025-07-30 08:44:59.526 [info] <0.273.0> Peer discovery backend rabbit_peer_discovery_classic_config does not support registration, skipping randomized startup delay. 2025-07-30 08:44:59.526 [info] <0.273.0> All discovered existing cluster peers: 2025-07-30 08:44:59.526 [info] <0.273.0> Discovered no peer nodes to cluster with. Some discovery backends can filter nodes out based on a readiness criteria. Enabling debug logging might help troubleshoot. 2025-07-30 08:44:59.533 [info] <0.44.0> Application mnesia exited with reason: stopped 2025-07-30 08:44:59.533 [info] <0.44.0> Application mnesia exited with reason: stopped 2025-07-30 08:44:59.553 [info] <0.44.0> Application mnesia started on node 'rabbit@LAPTOP-FU2L4D12' 2025-07-30 08:44:59.608 [info] <0.273.0> Waiting for Mnesia tables for 30000 ms, 9 retries left 2025-07-30 08:44:59.608 [info] <0.273.0> Successfully synced tables from a peer 2025-07-30 08:44:59.622 [info] <0.273.0> Waiting for Mnesia tables for 30000 ms, 9 retries left 2025-07-30 08:44:59.622 [info] <0.273.0> Successfully synced tables from a peer 2025-07-30 08:44:59.622 [info] <0.273.0> Feature flag `implicit_default_bindings`: supported, attempt to enable... 2025-07-30 08:44:59.622 [info] <0.273.0> Feature flag `implicit_default_bindings`: mark as enabled=state_changing 2025-07-30 08:44:59.626 [info] <0.273.0> Feature flags: list of feature flags found: 2025-07-30 08:44:59.626 [info] <0.273.0> Feature flags: [~] implicit_default_bindings 2025-07-30 08:44:59.627 [info] <0.273.0> Feature flags: [ ] maintenance_mode_status 2025-07-30 08:44:59.627 [info] <0.273.0> Feature flags: [ ] quorum_queue 2025-07-30 08:44:59.627 [info] <0.273.0> Feature flags: [ ] virtual_host_metadata 2025-07-30 08:44:59.627 [info] <0.273.0> Feature flags: feature flag states written to disk: yes 2025-07-30 08:44:59.643 [info] <0.273.0> Waiting for Mnesia tables for 30000 ms, 0 retries left 2025-07-30 08:44:59.643 [info] <0.273.0> Successfully synced tables from a peer 2025-07-30 08:44:59.643 [info] <0.273.0> Feature flag `implicit_default_bindings`: mark as enabled=true 2025-07-30 08:44:59.649 [info] <0.273.0> Feature flags: list of feature flags found: 2025-07-30 08:44:59.649 [info] <0.273.0> Feature flags: [x] implicit_default_bindings 2025-07-30 08:44:59.649 [info] <0.273.0> Feature flags: [ ] maintenance_mode_status 2025-07-30 08:44:59.649 [info] <0.273.0> Feature flags: [ ] quorum_queue 2025-07-30 08:44:59.649 [info] <0.273.0> Feature flags: [ ] virtual_host_metadata 2025-07-30 08:44:59.649 [info] <0.273.0> Feature flags: feature flag states written to disk: yes 2025-07-30 08:44:59.661 [info] <0.273.0> Feature flag `maintenance_mode_status`: supported, attempt to enable... 2025-07-30 08:44:59.661 [info] <0.273.0> Feature flag `maintenance_mode_status`: mark as enabled=state_changing 2025-07-30 08:44:59.665 [info] <0.273.0> Feature flags: list of feature flags found: 2025-07-30 08:44:59.665 [info] <0.273.0> Feature flags: [x] implicit_default_bindings 2025-07-30 08:44:59.666 [info] <0.273.0> Feature flags: [~] maintenance_mode_status 2025-07-30 08:44:59.666 [info] <0.273.0> Feature flags: [ ] quorum_queue 2025-07-30 08:44:59.666 [info] <0.273.0> Feature flags: [ ] virtual_host_metadata 2025-07-30 08:44:59.666 [info] <0.273.0> Feature flags: feature flag states written to disk: yes 2025-07-30 08:44:59.677 [info] <0.273.0> Creating table rabbit_node_maintenance_states for feature flag `maintenance_mode_status` 2025-07-30 08:44:59.680 [info] <0.273.0> Feature flag `maintenance_mode_status`: mark as enabled=true 2025-07-30 08:44:59.686 [info] <0.273.0> Feature flags: list of feature flags found: 2025-07-30 08:44:59.687 [info] <0.273.0> Feature flags: [x] implicit_default_bindings 2025-07-30 08:44:59.687 [info] <0.273.0> Feature flags: [x] maintenance_mode_status 2025-07-30 08:44:59.687 [info] <0.273.0> Feature flags: [ ] quorum_queue 2025-07-30 08:44:59.687 [info] <0.273.0> Feature flags: [ ] virtual_host_metadata 2025-07-30 08:44:59.687 [info] <0.273.0> Feature flags: feature flag states written to disk: yes 2025-07-30 08:44:59.699 [info] <0.273.0> Feature flag `quorum_queue`: supported, attempt to enable... 2025-07-30 08:44:59.699 [info] <0.273.0> Feature flag `quorum_queue`: mark as enabled=state_changing 2025-07-30 08:44:59.704 [info] <0.273.0> Feature flags: list of feature flags found: 2025-07-30 08:44:59.704 [info] <0.273.0> Feature flags: [x] implicit_default_bindings 2025-07-30 08:44:59.704 [info] <0.273.0> Feature flags: [x] maintenance_mode_status 2025-07-30 08:44:59.704 [info] <0.273.0> Feature flags: [~] quorum_queue 2025-07-30 08:44:59.704 [info] <0.273.0> Feature flags: [ ] virtual_host_metadata 2025-07-30 08:44:59.704 [info] <0.273.0> Feature flags: feature flag states written to disk: yes 2025-07-30 08:44:59.718 [info] <0.273.0> Waiting for Mnesia tables for 30000 ms, 9 retries left 2025-07-30 08:44:59.718 [info] <0.273.0> Successfully synced tables from a peer 2025-07-30 08:44:59.718 [info] <0.273.0> Feature flag `quorum_queue`: migrating Mnesia table rabbit_queue... 2025-07-30 08:44:59.734 [info] <0.273.0> Feature flag `quorum_queue`: migrating Mnesia table rabbit_durable_queue... 2025-07-30 08:44:59.751 [info] <0.273.0> Feature flag `quorum_queue`: Mnesia tables migration done 2025-07-30 08:44:59.751 [info] <0.273.0> Feature flag `quorum_queue`: mark as enabled=true 2025-07-30 08:44:59.755 [info] <0.273.0> Feature flags: list of feature flags found: 2025-07-30 08:44:59.756 [info] <0.273.0> Feature flags: [x] implicit_default_bindings 2025-07-30 08:44:59.756 [info] <0.273.0> Feature flags: [x] maintenance_mode_status 2025-07-30 08:44:59.756 [info] <0.273.0> Feature flags: [x] quorum_queue 2025-07-30 08:44:59.756 [info] <0.273.0> Feature flags: [ ] virtual_host_metadata 2025-07-30 08:44:59.756 [info] <0.273.0> Feature flags: feature flag states written to disk: yes 2025-07-30 08:44:59.772 [info] <0.273.0> Feature flag `virtual_host_metadata`: supported, attempt to enable... 2025-07-30 08:44:59.772 [info] <0.273.0> Feature flag `virtual_host_metadata`: mark as enabled=state_changing 2025-07-30 08:44:59.775 [info] <0.273.0> Feature flags: list of feature flags found: 2025-07-30 08:44:59.775 [info] <0.273.0> Feature flags: [x] implicit_default_bindings 2025-07-30 08:44:59.775 [info] <0.273.0> Feature flags: [x] maintenance_mode_status 2025-07-30 08:44:59.775 [info] <0.273.0> Feature flags: [x] quorum_queue 2025-07-30 08:44:59.775 [info] <0.273.0> Feature flags: [~] virtual_host_metadata 2025-07-30 08:44:59.776 [info] <0.273.0> Feature flags: feature flag states written to disk: yes 2025-07-30 08:44:59.786 [info] <0.273.0> Waiting for Mnesia tables for 30000 ms, 9 retries left 2025-07-30 08:44:59.786 [info] <0.273.0> Successfully synced tables from a peer 2025-07-30 08:44:59.807 [info] <0.273.0> Feature flag `virtual_host_metadata`: mark as enabled=true 2025-07-30 08:44:59.812 [info] <0.273.0> Feature flags: list of feature flags found: 2025-07-30 08:44:59.812 [info] <0.273.0> Feature flags: [x] implicit_default_bindings 2025-07-30 08:44:59.812 [info] <0.273.0> Feature flags: [x] maintenance_mode_status 2025-07-30 08:44:59.812 [info] <0.273.0> Feature flags: [x] quorum_queue 2025-07-30 08:44:59.812 [info] <0.273.0> Feature flags: [x] virtual_host_metadata 2025-07-30 08:44:59.812 [info] <0.273.0> Feature flags: feature flag states written to disk: yes 2025-07-30 08:44:59.823 [info] <0.273.0> Waiting for Mnesia tables for 30000 ms, 9 retries left 2025-07-30 08:44:59.824 [info] <0.273.0> Successfully synced tables from a peer 2025-07-30 08:44:59.842 [info] <0.273.0> Waiting for Mnesia tables for 30000 ms, 9 retries left 2025-07-30 08:44:59.842 [info] <0.273.0> Successfully synced tables from a peer 2025-07-30 08:44:59.842 [info] <0.273.0> Peer discovery backend rabbit_peer_discovery_classic_config does not support registration, skipping registration. 2025-07-30 08:44:59.842 [info] <0.273.0> Running boot step database_sync defined by app rabbit 2025-07-30 08:44:59.842 [info] <0.273.0> Running boot step feature_flags defined by app rabbit 2025-07-30 08:44:59.843 [info] <0.273.0> Running boot step codec_correctness_check defined by app rabbit 2025-07-30 08:44:59.843 [info] <0.273.0> Running boot step external_infrastructure defined by app rabbit 2025-07-30 08:44:59.843 [info] <0.273.0> Running boot step rabbit_registry defined by app rabbit 2025-07-30 08:44:59.843 [info] <0.273.0> Running boot step rabbit_auth_mechanism_cr_demo defined by app rabbit 2025-07-30 08:44:59.843 [info] <0.273.0> Running boot step rabbit_queue_location_random defined by app rabbit 2025-07-30 08:44:59.843 [info] <0.273.0> Running boot step rabbit_event defined by app rabbit 2025-07-30 08:44:59.843 [info] <0.273.0> Running boot step rabbit_auth_mechanism_amqplain defined by app rabbit 2025-07-30 08:44:59.843 [info] <0.273.0> Running boot step rabbit_auth_mechanism_plain defined by app rabbit 2025-07-30 08:44:59.843 [info] <0.273.0> Running boot step rabbit_exchange_type_direct defined by app rabbit 2025-07-30 08:44:59.843 [info] <0.273.0> Running boot step rabbit_exchange_type_fanout defined by app rabbit 2025-07-30 08:44:59.843 [info] <0.273.0> Running boot step rabbit_exchange_type_headers defined by app rabbit 2025-07-30 08:44:59.843 [info] <0.273.0> Running boot step rabbit_exchange_type_topic defined by app rabbit 2025-07-30 08:44:59.843 [info] <0.273.0> Running boot step rabbit_mirror_queue_mode_all defined by app rabbit 2025-07-30 08:44:59.843 [info] <0.273.0> Running boot step rabbit_mirror_queue_mode_exactly defined by app rabbit 2025-07-30 08:44:59.843 [info] <0.273.0> Running boot step rabbit_mirror_queue_mode_nodes defined by app rabbit 2025-07-30 08:44:59.843 [info] <0.273.0> Running boot step rabbit_priority_queue defined by app rabbit 2025-07-30 08:44:59.843 [info] <0.273.0> Priority queues enabled, real BQ is rabbit_variable_queue 2025-07-30 08:44:59.843 [info] <0.273.0> Running boot step rabbit_queue_location_client_local defined by app rabbit 2025-07-30 08:44:59.844 [info] <0.273.0> Running boot step rabbit_queue_location_min_masters defined by app rabbit 2025-07-30 08:44:59.844 [info] <0.273.0> Running boot step kernel_ready defined by app rabbit 2025-07-30 08:44:59.844 [info] <0.273.0> Running boot step rabbit_sysmon_minder defined by app rabbit 2025-07-30 08:44:59.844 [info] <0.273.0> Running boot step rabbit_epmd_monitor defined by app rabbit 2025-07-30 08:44:59.845 [info] <0.605.0> epmd monitor knows us, inter-node communication (distribution) port: 25672 2025-07-30 08:44:59.845 [info] <0.273.0> Running boot step guid_generator defined by app rabbit 2025-07-30 08:44:59.848 [info] <0.273.0> Running boot step rabbit_node_monitor defined by app rabbit 2025-07-30 08:44:59.848 [info] <0.609.0> Starting rabbit_node_monitor 2025-07-30 08:44:59.848 [info] <0.273.0> Running boot step delegate_sup defined by app rabbit 2025-07-30 08:44:59.848 [info] <0.273.0> Running boot step rabbit_memory_monitor defined by app rabbit 2025-07-30 08:44:59.849 [info] <0.273.0> Running boot step core_initialized defined by app rabbit 2025-07-30 08:44:59.849 [info] <0.273.0> Running boot step upgrade_queues defined by app rabbit 2025-07-30 08:44:59.859 [info] <0.273.0> message_store upgrades: 1 to apply 2025-07-30 08:44:59.859 [info] <0.273.0> message_store upgrades: Applying rabbit_variable_queue:move_messages_to_vhost_store 2025-07-30 08:44:59.859 [info] <0.273.0> message_store upgrades: No durable queues found. Skipping message store migration 2025-07-30 08:44:59.859 [info] <0.273.0> message_store upgrades: Removing the old message store data 2025-07-30 08:44:59.860 [info] <0.273.0> message_store upgrades: All upgrades applied successfully 2025-07-30 08:44:59.878 [info] <0.273.0> Running boot step rabbit_connection_tracking defined by app rabbit 2025-07-30 08:44:59.879 [info] <0.273.0> Running boot step rabbit_connection_tracking_handler defined by app rabbit 2025-07-30 08:44:59.879 [info] <0.273.0> Running boot step rabbit_exchange_parameters defined by app rabbit 2025-07-30 08:44:59.879 [info] <0.273.0> Running boot step rabbit_mirror_queue_misc defined by app rabbit 2025-07-30 08:44:59.879 [info] <0.273.0> Running boot step rabbit_policies defined by app rabbit 2025-07-30 08:44:59.880 [info] <0.273.0> Running boot step rabbit_policy defined by app rabbit 2025-07-30 08:44:59.880 [info] <0.273.0> Running boot step rabbit_queue_location_validator defined by app rabbit 2025-07-30 08:44:59.880 [info] <0.273.0> Running boot step rabbit_quorum_memory_manager defined by app rabbit 2025-07-30 08:44:59.880 [info] <0.273.0> Running boot step rabbit_vhost_limit defined by app rabbit 2025-07-30 08:44:59.880 [info] <0.273.0> Running boot step recovery defined by app rabbit 2025-07-30 08:44:59.881 [info] <0.273.0> Running boot step empty_db_check defined by app rabbit 2025-07-30 08:44:59.881 [info] <0.273.0> Will seed default virtual host and user... 2025-07-30 08:44:59.881 [info] <0.273.0> Adding vhost '/' (description: 'Default virtual host') 2025-07-30 08:44:59.886 [info] <0.646.0> Making sure data directory 'd:/Downloads/RabbitMQData/db/rabbit@LAPTOP-FU2L4D12-mnesia/msg_stores/vhosts/628WB79CIFDYO9LJI6DKMI09L' for vhost '/' exists 2025-07-30 08:44:59.889 [info] <0.646.0> Starting message stores for vhost '/' 2025-07-30 08:44:59.889 [info] <0.650.0> Message store "628WB79CIFDYO9LJI6DKMI09L/msg_store_transient": using rabbit_msg_store_ets_index to provide index 2025-07-30 08:44:59.891 [info] <0.646.0> Started message store of type transient for vhost '/' 2025-07-30 08:44:59.891 [info] <0.654.0> Message store "628WB79CIFDYO9LJI6DKMI09L/msg_store_persistent": using rabbit_msg_store_ets_index to provide index 2025-07-30 08:44:59.892 [warning] <0.654.0> Message store "628WB79CIFDYO9LJI6DKMI09L/msg_store_persistent": rebuilding indices from scratch 2025-07-30 08:44:59.893 [info] <0.646.0> Started message store of type persistent for vhost '/' 2025-07-30 08:44:59.896 [info] <0.273.0> Created user 'guest' 2025-07-30 08:44:59.896 [info] <0.273.0> Successfully set user tags for user 'guest' to [administrator] 2025-07-30 08:44:59.897 [info] <0.273.0> Successfully set permissions for 'guest' in virtual host '/' to '.*', '.*', '.*' 2025-07-30 08:44:59.897 [info] <0.273.0> Running boot step rabbit_looking_glass defined by app rabbit 2025-07-30 08:44:59.897 [info] <0.273.0> Running boot step rabbit_core_metrics_gc defined by app rabbit 2025-07-30 08:44:59.897 [info] <0.273.0> Running boot step background_gc defined by app rabbit 2025-07-30 08:44:59.897 [info] <0.273.0> Running boot step connection_tracking defined by app rabbit 2025-07-30 08:44:59.900 [info] <0.273.0> Setting up a table for connection tracking on this node: 'tracked_connection_on_node_rabbit@LAPTOP-FU2L4D12' 2025-07-30 08:44:59.902 [info] <0.273.0> Setting up a table for per-vhost connection counting on this node: 'tracked_connection_per_vhost_on_node_rabbit@LAPTOP-FU2L4D12' 2025-07-30 08:44:59.902 [info] <0.273.0> Running boot step routing_ready defined by app rabbit 2025-07-30 08:44:59.902 [info] <0.273.0> Running boot step pre_flight defined by app rabbit 2025-07-30 08:44:59.902 [info] <0.273.0> Running boot step notify_cluster defined by app rabbit 2025-07-30 08:44:59.902 [info] <0.273.0> Running boot step networking defined by app rabbit 2025-07-30 08:44:59.902 [info] <0.273.0> Running boot step definition_import_worker_pool defined by app rabbit 2025-07-30 08:44:59.902 [info] <0.351.0> Starting worker pool 'definition_import_pool' with 8 processes in it 2025-07-30 08:44:59.902 [info] <0.273.0> Running boot step cluster_name defined by app rabbit 2025-07-30 08:44:59.902 [info] <0.273.0> Initialising internal cluster ID to 'rabbitmq-cluster-id-vb7eUVm_pMu4vzxKD3W8-A' 2025-07-30 08:44:59.903 [info] <0.273.0> Running boot step direct_client defined by app rabbit 2025-07-30 08:44:59.903 [info] <0.44.0> Application rabbit started on node 'rabbit@LAPTOP-FU2L4D12' 2025-07-30 08:45:00.001 [info] <0.699.0> Ready to start client connection listeners 2025-07-30 08:45:00.015 [info] <0.714.0> started TCP listener on [::]:5672 2025-07-30 08:45:00.017 [info] <0.729.0> started TCP listener on 0.0.0.0:5672 2025-07-30 08:45:00.018 [notice] <0.282.0> Changed loghwm of d:/Downloads/RabbitMQData/log/rabbit@LAPTOP-FU2L4D12.log to 5000 2025-07-30 08:45:00.195 [info] <0.699.0> Server startup complete; 0 plugins started. 2025-07-30 08:45:00.195 [info] <0.699.0> Resetting node maintenance status
07-31
源码来自:https://pan.quark.cn/s/a4b39357ea24 ### 操作指南:洗衣机使用方法详解#### 1. 启动与水量设定- **使用方法**:使用者必须首先按下洗衣设备上的“启动”按键,同时依据衣物数量设定相应的“水量选择”旋钮(高、中或低水量)。这一步骤是洗衣机运行程序的开端。- **运作机制**:一旦“启动”按键被触发,洗衣设备内部的控制系统便会启动,通过感应器识别水量选择旋钮的位置,进而确定所需的水量高度。- **技术执行**:在当代洗衣设备中,这一流程一般由微处理器掌管,借助电磁阀调控进水量,直至达到指定的高度。#### 2. 进水过程- **使用说明**:启动后,洗衣设备开始进水,直至达到所选的水位(高、中或低)。- **技术参数**:水量的监测通常采用浮子式水量控制器或压力感应器来实现。当水位达到预定值时,进水阀会自动关闭,停止进水。- **使用提醒**:务必确保水龙头已开启,并检查水管连接是否牢固,以防止漏水。#### 3. 清洗过程- **使用步骤**:2秒后,洗衣设备进入清洗环节。在此期间,滚筒会执行一系列正转和反转的动作: - 正转25秒 - 暂停3秒 - 反转25秒 - 再次暂停3秒- **重复次数**:这一系列动作将重复执行5次,总耗时为280秒。- **技术关键**:清洗环节通过电机驱动滚筒旋转,利用水流冲击力和洗衣液的化学效果,清除衣物上的污垢。#### 4. 排水与甩干- **使用步骤**:清洗结束后,洗衣设备会自动进行排水,将污水排出,然后进入甩干阶段,甩干时间为30秒。- **技术应用**:排水是通过泵将水抽出洗衣设备;甩干则是通过高速旋转滚筒,利用离心力去除衣物上的水分。- **使用提醒**:...
代码下载地址: https://pan.quark.cn/s/c289368a8f5c 在安卓应用开发领域,构建一个高效且用户友好的聊天系统是一项核心任务。 为了协助开发者们迅速达成这一目标,本文将分析几种常见的安卓聊天框架,并深入说明它们的功能特性、应用方法及主要优势。 1. **环信(Easemob)** 环信是一个专为移动应用打造的即时通讯软件开发套件,涵盖了文本、图片、语音、视频等多种消息形式。 通过整合环信SDK,开发者能够迅速构建自身的聊天平台。 环信支持消息内容的个性化定制,能够应对各种复杂的应用场景,并提供多样的API接口供开发者使用。 2. **融云(RongCloud)** 融云作为国内领先的IM云服务企业,提供了全面的聊天解决方案,包括一对一交流、多人群聊、聊天空间等。 融云的突出之处在于其稳定运行和高并发处理性能,以及功能完备的后台管理工具,便于开发者执行用户管理、消息发布等操作。 再者,融云支持多种消息格式,如位置信息、文件传输、表情符号等,显著增强了用户聊天体验。 3. **Firebase Cloud Messaging(FCM)** FCM由Google提供的云端消息传递服务,可达成安卓设备与服务器之间的即时数据交换。 虽然FCM主要应用于消息推送,但配合Firebase Realtime Database或Firestore数据库,开发者可以开发基础的聊天软件。 FCM的显著优势在于其全球性的推送网络,保障了消息能够及时且精确地传输至用户。 4. **JMessage(极光推送)** 极光推送是一款提供消息发布服务的软件开发工具包,同时具备基础的即时通讯能力。 除了常规的文字、图片信息外,极光推送还支持个性化消息,使得开发者能够实现更为复杂的聊天功能。 此...
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符  | 博主筛选后可见
 
红包 添加红包
表情包 插入表情
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值