CN111026564A - Naming service processing method and system - Google Patents
Naming service processing method and system Download PDFInfo
- Publication number
- CN111026564A CN111026564A CN201911138963.7A CN201911138963A CN111026564A CN 111026564 A CN111026564 A CN 111026564A CN 201911138963 A CN201911138963 A CN 201911138963A CN 111026564 A CN111026564 A CN 111026564A
- Authority
- CN
- China
- Prior art keywords
- service
- target
- item
- name
- naming
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/546—Message passing systems or structures, e.g. queues
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/547—Remote procedure calls [RPC]; Web services
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The invention belongs to the technical field of computer application, and relates to a naming service processing method and system. The method comprises the following steps: receiving a request message sent by a target interface of a client, wherein the request message at least comprises a service name and a service version of a target service item which is requested to be processed, and the service type corresponding to the target interface comprises any one of a registration service, a logout service and a query service; processing the target service item according to the service type corresponding to the target interface, and the service name and the service version of the target service item; and sending a reply message to the client, wherein the reply message at least comprises a request completion state and a service provider ID. By the method provided by the embodiment of the disclosure, the expandability of the microkernel operating system is effectively improved.
Description
Technical Field
The invention belongs to the technical field of computer application, and particularly relates to a naming service processing method and a naming service processing system.
Background
In order to improve the scalability of the microkernel operating system, the microkernel itself usually provides only a basic mechanism and does not provide related policies, so that the operating system needs to create several management tasks, which serve as service providers for providing some related services and implementing related policies. The microkernel operating system needs to provide a corresponding method to control these management tasks.
Therefore, a solution for managing multiple request tasks of multiple clients in an operating system is needed.
Disclosure of Invention
In order to solve the above technical problem, an embodiment of the present invention provides a method and a system for processing a naming service, which specifically include:
in a first aspect, an embodiment of the present disclosure provides a method for processing a naming service, including:
receiving a request message sent by a target interface of a client, wherein the request message at least comprises a service name and a service version of a target service item which is requested to be processed, and the service type corresponding to the target interface comprises any one of a registration service, a logout service and a query service;
processing the target service item according to the service type corresponding to the target interface, and the service name and the service version of the target service item;
and sending a reply message to the client, wherein the reply message at least comprises a request completion state and a service provider ID.
Optionally, the step of processing the target service item according to the service type corresponding to the target interface, and the service name and the service version of the target service item includes:
if the service type corresponding to the target interface is a registration service, executing registration operation on the target service item according to the service name and the service version of the target service item;
if the service type corresponding to the target interface is query service, executing query operation on the target service item according to the service name and the service version of the target service item;
and if the service type corresponding to the target interface is a logout service, executing logout operation on the target service item according to the service name and the service version of the target service item.
Optionally, before the step of receiving the request message sent by the target interface of the client, the method further includes:
judging whether the request completion state of the prior request message of the target interface is completed or not;
and if the request completion state of the previous request message of the target interface is completed, clearing the ID of the previous request message of the target interface.
Optionally, if the service type corresponding to the target interface is a registration service, the step of performing a registration operation on the target service item according to the service name and the service version of the target service item includes:
traversing a naming service database, and determining whether the service name and the version number of the target service item are registered;
if the service name and the version number of the target service item are not registered, registering the service name and the version number of the target service item into the naming service database to obtain the provider ID of the target service item;
and if the service name and the version number of the target service item are registered, acquiring the provider ID of the target service item.
Optionally, if the service type corresponding to the target interface is a query service, the step of executing a query operation on the target service item according to the service name and the service version of the target service item includes:
traversing the named service database, and inquiring whether the target service item exists according to the service name and the service version number;
if the target service item exists, determining that the query is successful;
if the target service item does not exist, registering the service name and the service version of the target service item in the naming service database, and determining that the registration and the query are successful.
Optionally, if the service type corresponding to the target interface is a logout service, the step of performing a logout operation on the target service item according to the service name and the service version of the target service item includes:
traversing the named service database, and searching whether the target service item exists according to the service name and the service version number;
and if the target service item exists, deleting the service provider corresponding to the target service item from the naming service database.
Optionally, before the step of registering the service name and the version number of the target service item in the naming service database, if the service name and the version number of the target service item are not registered, the method further includes:
if the service name and the version number of the target service item are not registered, adding a task waiting for registration corresponding to the target service item in a naming service waiting registration linked list;
if the service name and the version number of the target service item are not registered, the service name and the version number of the target service item are registered in the naming service database, and after the step of obtaining the provider ID of the target service item, the method further comprises:
inquiring whether a waiting registration task corresponding to the target service item exists in the waiting registration chain of the naming service;
and if so, deleting the task waiting for registration corresponding to the target service item from the naming service waiting registration chain.
Optionally, before the step of receiving the request message sent by the target interface of the client, the method further includes:
when an operating system is initialized, a root task for monitoring the partitioned operating system is established;
and creating a naming service task inside the root task, wherein the naming service task has higher priority than other service tasks in the root task.
In a second aspect, an embodiment of the present invention further provides a method for processing a naming service, where the method is applied to a client, and the method includes:
determining the service type, the service name and the service version number of a target service item requested to be processed according to the input of a user;
and sending a request message through a target interface corresponding to the service type of the target service item, wherein the request message at least comprises the service name and the service version of the target service item.
In a third aspect, an embodiment of the present invention further provides a system for processing a naming service, including a server and a client; wherein the content of the first and second substances,
the client is used for determining the service type, the service name and the service version number of a target service item requesting for processing according to the input of a user, and sending a request message through a target interface corresponding to the service type of the target service item, wherein the request message at least comprises the service name and the service version of the target service item, and the service type corresponding to the target interface comprises any one of a registration service, a logout service and an inquiry service;
the server is used for processing the target service item and sending a reply message to the client according to the service type corresponding to the target interface, the service name and the service version of the target service item, wherein the reply message at least comprises a request completion state and a service provider ID.
Drawings
Fig. 1 is a schematic flowchart of a naming service method according to an embodiment of the present invention;
fig. 2 is a schematic diagram of a naming service initialization process of a naming service method according to an embodiment of the present invention;
fig. 3 is a schematic diagram of a naming service task processing framework of a naming service method according to an embodiment of the present invention;
fig. 4 is a schematic diagram illustrating a registration service implementation process of the naming service method according to the embodiment of the present invention;
fig. 5 is a schematic diagram of a query service implementation process of the naming service method according to the embodiment of the present invention.
Detailed Description
Referring to fig. 1, a flowchart of a method for processing a naming service according to an embodiment of the present invention is shown. As shown in fig. 1, the processing method of the naming service mainly includes the following steps:
s101, receiving a request message sent by a target interface of a client; the request message at least comprises a service name and a service version of a target service item which is requested to be processed, and the service type corresponding to the target interface comprises any one of a registration service, a logout service and a query service;
the method for processing the naming service provided by the embodiment is applied to a server, and is used for realizing a process of processing the naming service requested by the client by the server, in particular to a microkernel operating system. Typical management tasks in microkernel operating systems typically implement complex control policies, such as core management tasks being responsible for handling service requests of the local CPU; the partition management task is responsible for service requests such as partition creation and deletion. If these control strategies are placed in the kernel, the kernel becomes very large and does not conform to the design principles of the microkernel operating system. The typical os management tasks like those described above are used to implement the control policy associated with the os, and may be placed outside the microkernel as a service provider, and the microkernel only retains basic mechanisms such as system initialization, handling of the renaming services, scheduling, communication, interrupt management, time management, memory management, system call, and the like. The naming service is used for controlling the management tasks of the typical operating system, so that the naming service can better serve the microkernel and the expandability of the microkernel operating system is improved.
Request message sent by client to server: including the members of the message header, request type, service name, service version, maximum latency, request options, etc. Among them, the request type can be divided into three types: a registration service, a deregistration service and a query service.
S102, processing the target service item according to the service type corresponding to the target interface, the service name and the service version of the target service item;
operation of the server, naming of the service database: organized as a singly linked list structure including members of service name, service version, service provider, next node pointer, etc.
For multiple users, the naming service registers the waiting chain: each task in the operating system has a registration waiting chain, and the registration waiting chains are organized into a unidirectional linked list structure and comprise members such as service names, name lengths, tasks waiting for registration, next node pointers and the like.
S103, sending a reply message to the client; wherein the reply message includes at least a request completion status and a service provider ID.
The reply message of the server to the client is as follows: including members of the message header, request completion status, service provider ID, etc.
Optionally, before the step of receiving the request message sent by the target interface of the client, the method further includes:
when an operating system is initialized, a root task for monitoring the partitioned operating system is established;
and creating a naming service task inside the root task, wherein the naming service task has higher priority than other service tasks in the root task.
Specifically, the server-side processing procedure includes the following steps:
2.1 naming service initialization
Starting a naming service task in an initialization process, creating 1 root task for an operating system, wherein the root task is responsible for monitoring a partition operating system, the priority is set to be the highest (set to be 0), the root task creates 1 internal naming service task, the priority is set to be the second highest (set to be 1) which is higher than or equal to other subtasks in the root task, the naming service tasks are added into a ready queue of a scheduler according to the priority, and the ready queue is responsible for blocking-type processing of received naming service requests, as shown in fig. 2.
2.2 naming service task processing framework
The naming service task is used for blocking the received naming service request. The processing frame is as follows: initializing a naming service database, processing all received naming service requests in a blocking mode in a circulating structure, emptying the ID of the last request message, receiving a new service request message from a sender, acquiring the ID of the new message, and replying a failure message if the acquired ID of the message is wrong; otherwise, if the acquired message ID is correct, the request message type is parsed, and the registration, cancellation, inquiry, and dump services are classified (the dump service is enabled on condition that the print request message is configured), and the above process is repeated all the time, as shown in fig. 3.
The service types include registration, deregistration, inquiry, dump implementation methods, which will be explained in detail below.
In a specific embodiment, the step of processing the target service item according to the service type corresponding to the target interface, and the service name and the service version of the target service item includes:
if the service type corresponding to the target interface is a registration service, executing registration operation on the target service item according to the service name and the service version of the target service item;
if the service type corresponding to the target interface is query service, executing query operation on the target service item according to the service name and the service version of the target service item;
and if the service type corresponding to the target interface is a logout service, executing logout operation on the target service item according to the service name and the service version of the target service item.
Optionally, before the step of receiving the request message sent by the target interface of the client, the method further includes:
judging whether the request completion state of the prior request message of the target interface is completed or not;
and if the request completion state of the previous request message of the target interface is completed, clearing the ID of the previous request message of the target interface.
Optionally, if the service type corresponding to the target interface is a registration service, the step of performing a registration operation on the target service item according to the service name and the service version of the target service item includes:
traversing a naming service database, and determining whether the service name and the version number of the target service item are registered;
if the service name and the version number of the target service item are not registered, registering the service name and the version number of the target service item into the naming service database to obtain the provider ID of the target service item;
and if the service name and the version number of the target service item are registered, acquiring the provider ID of the target service item.
When the registration service is realized, the validity of the name/version number of the service to be registered needs to be checked, the naming service database is traversed to confirm the uniqueness of the name/version number of the service to be registered, the position of the last node in the linked list is recorded, a new naming service database node is applied to be allocated, the node is filled and hung on the existing naming service database linked list, a message that the registration is successful is replied to a sender, the naming service waiting registration linked list is traversed, if a matched waiting task is found, the node is deleted from the naming service waiting registration linked list, and the allocated resource is released, as shown in fig. 3.
Optionally, if the service type corresponding to the target interface is a query service, the step of executing a query operation on the target service item according to the service name and the service version of the target service item includes:
traversing the named service database, and inquiring whether the target service item exists according to the service name and the service version number;
if the target service item exists, determining that the query is successful;
if the target service item does not exist, registering the service name and the service version of the target service item in the naming service database, and determining that the registration and the query are successful.
When the method is implemented at a server side, firstly checking whether the service name is valid, then traversing a naming service database, inquiring a matched service item according to the service name/service version, and if the matched service item is found, successfully replying to a service requester; otherwise, if the naming service task needs to wait for registration service in query, inserting the naming service task into a registration waiting chain and returning to success; if the naming service task does not wait to register for a service, a failure is returned to the service request task, indicating that the specified service was not found, as shown in FIG. 5.
Optionally, if the service type corresponding to the target interface is a logout service, the step of performing a logout operation on the target service item according to the service name and the service version of the target service item includes:
traversing the named service database, and searching whether the target service item exists according to the service name and the service version number;
and if the target service item exists, deleting the service provider corresponding to the target service item from the naming service database.
The logout service deletes the specified service provider from the naming service database, which is implemented as the inverse of the registration service process.
Optionally, before the step of registering the service name and the version number of the target service item in the naming service database, if the service name and the version number of the target service item are not registered, the method further includes:
if the service name and the version number of the target service item are not registered, adding a task waiting for registration corresponding to the target service item in a naming service waiting registration linked list;
if the service name and the version number of the target service item are not registered, the service name and the version number of the target service item are registered in the naming service database, and after the step of obtaining the provider ID of the target service item, the method further comprises:
inquiring whether a waiting registration task corresponding to the target service item exists in the waiting registration chain of the naming service;
and if so, deleting the task waiting for registration corresponding to the target service item from the naming service waiting registration chain.
Dump service: the contents of the naming service database are stored on the system console. Firstly, contents in a naming service database are traversed and printed, then, contents of a registration waiting chain are printed, and finally, a success is replied to a service requester to indicate that dump service is completed.
The client of the naming service provides interfaces for registration, cancellation and query services, and these interfaces fill the request message structure to form a request message and send it to the naming service task for processing.
3.1 registration interface: the interface caller is registered with the naming service system as a provider of the specified service. Services are represented by ASCII string names and numeric version numbers, allowing registration of a service with multiple implementations of the service. The client is implemented by sending a registration request to the naming service task.
3.2 query interface: the naming service system is used to query the service provider ID for a given service, which is represented by an ASCII string name and a numeric version number, and when querying for a matching service, both the service name and version number must match. The client is implemented by sending a query request to the naming service task.
3.3 interface logout: when a caller logs out a service from a named service system, the caller no longer serves as a provider of the specified service, the service is represented by an ASCII character string name and a number version number, and if the caller registers a plurality of versions of the service, each version of the service must be logged out. The client is implemented by sending a logout request to the naming service task.
The method provided by the embodiment of the invention can greatly improve the expandability of the microkernel operating system.
The following takes the core management task in the microkernel operating system as an example to illustrate the specific implementation of the naming service method in the present invention, and refer to fig. 2 to 5.
The naming service method designed by the invention is completed by the following three main steps:
step 1, naming service key data structure design
The naming service method comprises the following four key data structures:
1.1 request message: including the members of the message header, request type, service name, service version, maximum latency, request options, etc. Among them, the request type can be divided into three types: a registration service, a deregistration service and a query service.
1.2 reply message: including members of the message header, request completion status, service provider ID, etc.
1.3 naming service database: organized as a singly linked list structure including members of service name, service version, service provider, next node pointer, etc.
1.4 naming service registration waiting chain: each task in the operating system has a registration waiting chain, and the registration waiting chains are organized into a unidirectional linked list structure and comprise members such as service names, name lengths, tasks waiting for registration, next node pointers and the like.
Step 2, server end processing process
2.1 naming service initialization
Starting a naming service task in an initialization process, creating a root task, wherein the root task is responsible for monitoring a partition operating system, the priority is set to be highest (set to be 0), the root task creates an internal naming service task, the priority is set to be next highest (set to be 1), the root task is added into a ready queue of a scheduler according to the priority, and the ready queue is responsible for blocking processing of received naming service requests, as shown in fig. 1.
A core management task is created in the root task for each core of the multicore processor, and the properties of each core management task are set, including task name (e.g., coreMgr0, coreMgr1, …), task entry point, task priority (set to 1), task stack size (e.g., 4K), and CPU affinity (e.g., 0, 1, …).
2.2 naming service task processing framework
The naming service task is used for blocking the received naming service request. The processing frame is as follows: initializing a naming service database, processing all received naming service requests in a blocking mode in a circulating structure, emptying the ID of the last request message, receiving a new service request message from a sender, acquiring the ID of the new message, and replying a failure message if the acquired ID of the message is wrong; otherwise, if the acquired message ID is correct, the request message type is parsed, and the registration, cancellation, inquiry, and dump services are classified (the dump service is enabled on condition that the print request message is configured), and the above process is repeated all the time, as shown in fig. 2.
2.3. Service registration, cancellation, inquiry and dump realizing method
And (3) registration service: when the registration service is realized, the validity of the name/version number of the service to be registered needs to be checked, the naming service database is traversed to confirm the uniqueness of the name/version number of the service to be registered, the position of the last node in the linked list is recorded, a new naming service database node is applied to be allocated, the node is filled and hung on the existing naming service database linked list, a message that the registration is successful is replied to a sender, the naming service waiting registration linked list is traversed, if a matched waiting task is found, the node is deleted from the naming service waiting registration linked list, and the allocated resource is released, as shown in fig. 3.
Logout service: the logout service deletes the specified service provider from the naming service database, which is implemented as the inverse of the registration service process.
And (3) query service: when the method is implemented at a server side, firstly checking whether the service name is valid, then traversing a naming service database, inquiring a matched service item according to the service name/service version, and if the matched service item is found, successfully replying to a service requester; otherwise, if the naming service task needs to wait for registration service in query, inserting the naming service task into a registration waiting chain and returning to success; if the naming service task does not wait to register for a service, a failure is returned to the service request task, indicating that the specified service was not found, as shown in FIG. 4.
Dump service: the contents of the naming service database are stored on the system console. Firstly, contents in a naming service database are traversed and printed, then, contents of a registration waiting chain are printed, and finally, a success is replied to a service requester to indicate that dump service is completed.
Step 3, client processing procedure
The client of the naming service provides interfaces for registration, cancellation and query services, and these interfaces fill the request message structure to form a request message and send it to the naming service task for processing.
3.1 registration interface: the interface caller is registered with the naming service system as a provider of the specified service. Services are represented by ASCII string names and numeric version numbers, allowing registration of a service with multiple implementations of the service. The client is implemented by sending a registration request to the naming service task. The registration service is called at the beginning of the entry of the coreMgr of the core management task, the proper service name and version number are transmitted, and the coreMgr of the core management task is registered to a naming service system to be used as a provider of the corresponding service.
3.2 query interface: the naming service system is used to query the service provider ID for a given service, which is represented by an ASCII string name and a numeric version number, and when querying for a matching service, both the service name and version number must match. The client is implemented by sending a query request to the naming service task. When some control operations need to be completed by using the coreMgr, the query service must be called according to the coreMgr service name and the service version number of the core management task, and a request is sent to the naming service system to request the naming service system to provide the corresponding control operations. The application scenarios for invoking coreMgr query service include: control operations of the virtual cores (e.g., suspend the virtual cores, un-suspend the virtual cores, reset the virtual cores, post the virtual core interrupt), interrupt control operations (e.g., delete global interrupts), memory copy requests, cache operations (e.g., flush data cache, invalidate instruction cache), frame scheduling control operations (e.g., frame scheduling migration, get current frame scheduling name), event log control operations (e.g., start, stop), partition space operations (e.g., read from partition registers, write to partition registers, set partition CPUs), etc.
3.3 interface logout: when a caller logs out a service from a named service system, the caller no longer serves as a provider of the specified service, the service is represented by an ASCII character string name and a number version number, and if the caller registers a plurality of versions of the service, each version of the service must be logged out. The client side sends a logout request to the naming service task to achieve the effect achieved by the invention.
In addition, another naming service processing method is further provided in an embodiment of the present invention, which is different from the foregoing embodiment in that the naming service processing method provided in this embodiment is applied to a client, and the method includes:
determining the service type, the service name and the service version number of a target service item requested to be processed according to the input of a user;
and sending a request message through a target interface corresponding to the service type of the target service item, wherein the request message at least comprises the service name and the service version of the target service item.
In addition, the embodiment of the invention also provides a processing system of the naming service, which comprises a server and a client; wherein the content of the first and second substances,
the client is used for determining the service type, the service name and the service version number of a target service item requesting for processing according to the input of a user, and sending a request message through a target interface corresponding to the service type of the target service item, wherein the request message at least comprises the service name and the service version of the target service item, and the service type corresponding to the target interface comprises any one of a registration service, a logout service and an inquiry service;
the server is used for processing the target service item and sending a reply message to the client according to the service type corresponding to the target interface, the service name and the service version of the target service item, wherein the reply message at least comprises a request completion state and a service provider ID.
The specific implementation process of the naming service processing method and the naming service processing system provided in the embodiments of the present invention may refer to the specific implementation process of the above method embodiments, and are not described in detail again.
The above description is only for the specific embodiments of the present disclosure, but the scope of the present disclosure is not limited thereto, and any changes or substitutions that can be easily conceived by those skilled in the art within the technical scope of the present disclosure should be covered within the scope of the present disclosure. Therefore, the scope of protection not disclosed should be dominated by the scope of protection claimed.
Claims (10)
1. A method for processing a naming service, comprising:
receiving a request message sent by a target interface of a client, wherein the request message at least comprises a service name and a service version of a target service item which is requested to be processed, and the service type corresponding to the target interface comprises any one of a registration service, a logout service and a query service;
processing the target service item according to the service type corresponding to the target interface, and the service name and the service version of the target service item;
and sending a reply message to the client, wherein the reply message at least comprises a request completion state and a service provider ID.
2. The method of claim 1, wherein the step of processing the target service item according to the service type corresponding to the target interface, and the service name and the service version of the target service item comprises:
if the service type corresponding to the target interface is a registration service, executing registration operation on the target service item according to the service name and the service version of the target service item;
if the service type corresponding to the target interface is query service, executing query operation on the target service item according to the service name and the service version of the target service item;
and if the service type corresponding to the target interface is a logout service, executing logout operation on the target service item according to the service name and the service version of the target service item.
3. The method of claim 1, wherein the step of receiving the request message sent by the target interface of the client is preceded by the method further comprising:
judging whether the request completion state of the prior request message of the target interface is completed or not;
and if the request completion state of the previous request message of the target interface is completed, clearing the ID of the previous request message of the target interface.
4. The method according to any one of claims 1 to 3, wherein if the service type corresponding to the target interface is a registration service, the step of performing a registration operation on the target service item according to the service name and the service version of the target service item includes:
traversing a naming service database, and determining whether the service name and the version number of the target service item are registered;
if the service name and the version number of the target service item are not registered, registering the service name and the version number of the target service item into the naming service database to obtain the provider ID of the target service item;
and if the service name and the version number of the target service item are registered, acquiring the provider ID of the target service item.
5. The method according to claim 4, wherein if the service type corresponding to the target interface is query service, the step of performing query operation on the target service item according to the service name and the service version of the target service item includes:
traversing the named service database, and inquiring whether the target service item exists according to the service name and the service version number;
if the target service item exists, determining that the query is successful;
if the target service item does not exist, registering the service name and the service version of the target service item in the naming service database, and determining that the registration and the query are successful.
6. The method of claim 5, wherein if the service type corresponding to the target interface is a logout service, the step of performing a logout operation on the target service item according to the service name and the service version of the target service item comprises:
traversing the named service database, and searching whether the target service item exists according to the service name and the service version number;
and if the target service item exists, deleting the service provider corresponding to the target service item from the naming service database.
7. The method of claim 4, wherein before the step of registering the service name and version number of the target service item in the naming service database if the service name and version number of the target service item are not registered, the method further comprises:
if the service name and the version number of the target service item are not registered, adding a task waiting for registration corresponding to the target service item in a naming service waiting registration linked list;
if the service name and the version number of the target service item are not registered, the service name and the version number of the target service item are registered in the naming service database, and after the step of obtaining the provider ID of the target service item, the method further comprises:
inquiring whether a waiting registration task corresponding to the target service item exists in the waiting registration chain of the naming service;
and if so, deleting the task waiting for registration corresponding to the target service item from the naming service waiting registration chain.
8. The method of claim 1, wherein the step of receiving the request message sent by the target interface of the client is preceded by the method further comprising:
when an operating system is initialized, a root task for monitoring the partitioned operating system is established;
and creating a naming service task inside the root task, wherein the naming service task has higher priority than other service tasks in the root task.
9. A method for processing a naming service, applied to a client, the method comprising:
determining the service type, the service name and the service version number of a target service item requested to be processed according to the input of a user;
and sending a request message through a target interface corresponding to the service type of the target service item, wherein the request message at least comprises the service name and the service version of the target service item.
10. A processing system of a naming service is characterized by comprising a server and a client; wherein the content of the first and second substances,
the client is used for determining the service type, the service name and the service version number of a target service item requesting for processing according to the input of a user, and sending a request message through a target interface corresponding to the service type of the target service item, wherein the request message at least comprises the service name and the service version of the target service item, and the service type corresponding to the target interface comprises any one of a registration service, a logout service and an inquiry service;
the server is used for processing the target service item and sending a reply message to the client according to the service type corresponding to the target interface, the service name and the service version of the target service item, wherein the reply message at least comprises a request completion state and a service provider ID.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911138963.7A CN111026564A (en) | 2019-11-20 | 2019-11-20 | Naming service processing method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911138963.7A CN111026564A (en) | 2019-11-20 | 2019-11-20 | Naming service processing method and system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111026564A true CN111026564A (en) | 2020-04-17 |
Family
ID=70201596
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911138963.7A Pending CN111026564A (en) | 2019-11-20 | 2019-11-20 | Naming service processing method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111026564A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115658794A (en) * | 2022-12-09 | 2023-01-31 | 深圳高灯计算机科技有限公司 | Data query method and device, computer equipment and storage medium |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP0600235A1 (en) * | 1992-10-30 | 1994-06-08 | Software Ag | Cooperative processing interface and communication broker for heterogeneous computing environments |
| US6167427A (en) * | 1997-11-28 | 2000-12-26 | Lucent Technologies Inc. | Replication service system and method for directing the replication of information servers based on selected plurality of servers load |
| CN1971508A (en) * | 2006-12-01 | 2007-05-30 | 上海科泰世纪科技有限公司 | A naming service mechanism |
| CN105245595A (en) * | 2015-09-30 | 2016-01-13 | 小米科技有限责任公司 | Service response method and service response device |
| CN108153547A (en) * | 2017-12-26 | 2018-06-12 | 泰康保险集团股份有限公司 | Method for edition management, device, medium and the electronic equipment of micro services |
| CN108733406A (en) * | 2018-05-22 | 2018-11-02 | 山大地纬软件股份有限公司 | A kind of micro services development management system and method for supporting service upgrade edition compatibility |
| CN108762949A (en) * | 2018-05-21 | 2018-11-06 | 招银云创（深圳）信息技术有限公司 | Centralized dispatching method, system, computer equipment and storage medium |
-
2019
- 2019-11-20 CN CN201911138963.7A patent/CN111026564A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP0600235A1 (en) * | 1992-10-30 | 1994-06-08 | Software Ag | Cooperative processing interface and communication broker for heterogeneous computing environments |
| US6167427A (en) * | 1997-11-28 | 2000-12-26 | Lucent Technologies Inc. | Replication service system and method for directing the replication of information servers based on selected plurality of servers load |
| CN1971508A (en) * | 2006-12-01 | 2007-05-30 | 上海科泰世纪科技有限公司 | A naming service mechanism |
| CN105245595A (en) * | 2015-09-30 | 2016-01-13 | 小米科技有限责任公司 | Service response method and service response device |
| CN108153547A (en) * | 2017-12-26 | 2018-06-12 | 泰康保险集团股份有限公司 | Method for edition management, device, medium and the electronic equipment of micro services |
| CN108762949A (en) * | 2018-05-21 | 2018-11-06 | 招银云创（深圳）信息技术有限公司 | Centralized dispatching method, system, computer equipment and storage medium |
| CN108733406A (en) * | 2018-05-22 | 2018-11-02 | 山大地纬软件股份有限公司 | A kind of micro services development management system and method for supporting service upgrade edition compatibility |
Non-Patent Citations (1)
| Title |
|---|
| 桂肖敏等: "ARM与VxWorks在电力数据监测终端的应用", 电子工程师, pages 71 - 73 * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115658794A (en) * | 2022-12-09 | 2023-01-31 | 深圳高灯计算机科技有限公司 | Data query method and device, computer equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11409719B2 (en) | Co-locating microservice persistence containers within tenant-specific database | |
| JP5841177B2 (en) | Method and system for synchronization mechanism in multi-server reservation system | |
| US9405574B2 (en) | System and method for transmitting complex structures based on a shared memory queue | |
| CN103038788B (en) | Providing multiple network resources | |
| US6078955A (en) | Method for controlling a computer system including a plurality of computers and a network processed as a user resource | |
| US7657450B2 (en) | Reliable, secure and scalable infrastructure for event registration and propagation in a distributed enterprise | |
| US8131872B2 (en) | Affinity-based transaction processing | |
| JP5627187B2 (en) | Information processing apparatus, information processing method, and program | |
| US8615580B2 (en) | Message publication feedback in a publish/subscribe messaging environment | |
| CN109743411B (en) | Method, device and storage medium for dynamically scheduling IP proxy pool in distributed environment | |
| JP5705871B2 (en) | Resolving locks on distributed persistent instances | |
| US7836357B2 (en) | Error handling process | |
| US8856365B2 (en) | Computer-implemented method, computer system and computer readable medium | |
| CN103312624A (en) | Message queue service system and method | |
| JP5652480B2 (en) | Database update notification method | |
| US20210406102A1 (en) | Method and apparatus for providing asynchronicity to microservice application programming interfaces | |
| CN112073448A (en) | Service isolation method and device for dual-system terminal | |
| KR20040104467A (en) | Most eligible server in a common work queue environment | |
| US20030158939A1 (en) | Control device for file resources in a network | |
| US9473565B2 (en) | Data transmission for transaction processing in a networked environment | |
| CN111026564A (en) | Naming service processing method and system | |
| CN113645260A (en) | Service retry method, device, storage medium and electronic equipment | |
| US7441252B2 (en) | Cache control device, and method and computer program for the same | |
| CN114365109A (en) | RDMA-enabled key-value store | |
| CN113296872A (en) | Container state query method, device, equipment, storage medium and system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |