WO2015055073A1 - 一种消息提醒的方法和装置、以及*** - Google Patents

一种消息提醒的方法和装置、以及*** Download PDF

Info

Publication number
WO2015055073A1
WO2015055073A1 PCT/CN2014/087279 CN2014087279W WO2015055073A1 WO 2015055073 A1 WO2015055073 A1 WO 2015055073A1 CN 2014087279 W CN2014087279 W CN 2014087279W WO 2015055073 A1 WO2015055073 A1 WO 2015055073A1
Authority
WO
WIPO (PCT)
Prior art keywords
plug
message
client
operation interface
information
Prior art date
Application number
PCT/CN2014/087279
Other languages
English (en)
French (fr)
Inventor
曾溪泉
任寰
Original Assignee
北京奇虎科技有限公司
奇智软件（北京）有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 北京奇虎科技有限公司, 奇智软件（北京）有限公司 filed Critical 北京奇虎科技有限公司
Publication of WO2015055073A1 publication Critical patent/WO2015055073A1/zh

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/44—Arrangements for executing specific programs
    • G06F9/445—Program loading or initiating
    • G06F9/44521—Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
    • G06F9/44526—Plug-ins; Add-ons
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/21—Monitoring or handling of messages
    • H04L51/224—Monitoring or handling of messages providing notification on incoming messages, e.g. pushed notifications of received messages
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/55—Push-based network services

Definitions

  • the present application relates to the field of Internet technologies, and in particular, to a method and apparatus for message reminding, and a system.
  • the reminding mechanism for the webpage application or the webpage content is integrated directly into the application in the form of a plug-in or directly in the form of a function item; when the terminal device receives the reminder message of the webpage application or the webpage change
  • the alert message and data are sent directly to the plugin through the application programming interface (API), and processed by the plugin.
  • the above plugins include a microblog plugin, an email reminder plugin, and the like.
  • the Weibo plug-in directly displays information on the number of new Weibos, the number of new concerns, the number of new comments, and the like on the terminal device to remind the user according to the reminder message from the server.
  • the message reminder in the prior art is performed for each plug-in or one of the function items in the application.
  • the message reminding method has no scalability on the platform, which leads to upgrade complicated problems, such as need for each
  • the message reminding methods of the plug-in are all modified and upgraded to meet the requirements and lack of program scalability.
  • the present application has been made in order to provide a method and system for a message reminder that overcomes the above problems or at least partially solves the above problems, and a corresponding message reminder.
  • a method for message reminding which includes: a plug-in registers a message reminding event and an operation interface with a client; and when the client receives a notification message of a registered message reminding event sent by the server When the client sends a message to the plugin to return a message reminding event, and the plugin displays the message reminder according to the returned information; when the client receives the plugin sent When the request is manipulated, the client invokes the registered operation interface and responds to the operation request.
  • an apparatus for message reminding comprising: a registration module adapted to cause a plug-in to register a message reminding event and an operation interface; and a message reminding module adapted to receive a registration sent by the server When the message reminds the notification message of the event, the return information of the message reminding event is sent to the plug-in, and the plug-in displays the message reminding information according to the returned information; the calling module is adapted to call the registered operation interface when receiving the operation request sent by the plug-in, Respond to an operation request.
  • a system for message reminding including: the device for reminding the message of the present application, further comprising: a plug-in module and a server.
  • a computer program comprising computer readable code that, when executed on a computer, performs the aforementioned message alerting method.
  • a method and apparatus and system for message reminding of the present application by providing a client between the server and the plug-in, the client uniformly sends a reminder message from the server to each plug-in for processing, and the client gives Each plug-in provides a common operation interface to facilitate communication between the plug-in and the server, thereby solving the problem that the prior art message reminding method has no scalability on the platform, thereby causing the upgrade complicated problem, and obtaining a program extension for further improving the message reminding manner.
  • sexual benefits by providing a client between the server and the plug-in, the client uniformly sends a reminder message from the server to each plug-in for processing, and the client gives Each plug-in provides a common operation interface to facilitate communication between the plug-in and the server, thereby solving the problem that the prior art message reminding method has no scalability on the platform, thereby causing the upgrade complicated problem, and obtaining a program extension for further improving the message reminding manner.
  • FIG. 1 shows a flow chart of a method for message reminding according to a first embodiment of the present application
  • FIG. 2 is a flow chart showing a method of message reminding according to a second embodiment of the present application
  • FIG. 3 shows a flow chart of inter-process communication according to a second embodiment of the present application
  • FIG. 4 is a block diagram showing the structure of a message reminder according to a third embodiment of the present application.
  • FIG. 5 is a block diagram showing the structure of a message reminder according to a fourth embodiment of the present application.
  • FIG. 6 is a detailed structural diagram of a device for message reminding according to a fourth embodiment of the present application.
  • FIG. 7 is a system structural diagram showing a message reminder according to a fifth embodiment of the present application.
  • Figure 8 shows schematically a block diagram of an electronic device for performing the method according to the invention
  • Fig. 9 schematically shows a storage unit for holding or carrying program code implementing the method according to the invention.
  • FIG. 1 is a flowchart of a method for message reminding according to a first embodiment of the present application. As shown in FIG. 1, the method includes:
  • Step S101 The plug-in registers a message reminding event and an operation interface with the client.
  • a plug-in refers to an application that is installed in a main program of a terminal device and has a certain supplementary function, including but not limited to: various plug-ins of a browser, a chat software client plug-in, and a virtual machine desktop.
  • Plugins, email alert plugins, and other plugins with message alerting are a program that provides local services to customers when installed in a terminal device.
  • the terminal device may include: an electronic computer, a tablet computer, a mobile phone, and other devices capable of networking.
  • the above client is operated by a call of a main program, which is called a caller of the client, and includes but is not limited to: a browser, a chat software client, a virtual machine desktop client, or a mail client, that is, the above The software has the right to call the client.
  • a caller of the client includes but is not limited to: a browser, a chat software client, a virtual machine desktop client, or a mail client, that is, the above
  • the software has the right to call the client.
  • Step S102 When the client receives the notification message of the registered message reminding event sent by the server, the client sends a return message of the message reminding event to the plug-in, and the plug-in displays the message reminding information according to the returned information.
  • the server sends a notification message to the terminal device to notify that the message reminder event is triggered; when the client installed by the terminal device receives the notification message, The client determines whether it is a notification message of the registered message reminding event according to the registered message reminding event; if yes, it indicates that the registered message reminding event is triggered, and the client sends the return information of the message reminding event from the server.
  • Step S103 When the client receives the operation request sent by the plug-in, the client invokes the registered operation interface and responds to the operation request.
  • the plugin When the plugin needs to call the interface to communicate with the server, the plugin does not need to call its own interface, but sends an operation request to the client, and the client calls the operation interface provided by the client registered by the client, and then performs the operation with the server. Communicate and complete user-based plugin-based operations.
  • the client uniformly sends a reminder message from the server to each plug-in for processing, and the client provides the plug-in for each plug-in.
  • the universal operation interface facilitates communication between the plug-in and the server, thereby solving the problem that the prior art message reminding method lacks scalability on the platform, which leads to a complicated upgrade problem.
  • you need to upgrade the message reminder function you do not need to upgrade for each plug-in, only the client can be upgraded.
  • the client-based message reminding method has little influence on the program architecture, and the program modification can be performed only on the client side, and it is not necessary to change the program of each plug-in.
  • the startup client can have three startup modes, which are step S211, step S212, and step S213, respectively.
  • Step S211 when the plug-in is started, the client is started;
  • Step S212 When the caller of the client starts, start the client;
  • Step S213 the plug-in queries the handle of the client's message window; when the plug-in does not query the handle of the client's message window, the client is started.
  • the client can be started before the plug-in works, so that the plug-in can process the message reminder through the client.
  • the above three startup modes mainly describe the timing of starting the client.
  • the application is not limited to the above three startup modes, and other startup modes may be set according to requirements.
  • step S212 or step S213 the method in this embodiment further includes:
  • Step S221 The client broadcasts a registration request to each plug-in, so that each plug-in responds to the registration request and performs registration of the message reminding event and the operation interface.
  • the plug-in can register the message reminding event and the operation interface by broadcasting, so as to prevent the plug-in from being missed by the client.
  • the plug-in of the present application registers the message reminder event and the operation interface with the client not only based on the above broadcast mode.
  • Step S201 The plug-in registers a message reminding event and an operation interface with the client.
  • the message reminding events include but are not limited to: receiving new reminders, modifying the account list, setting changes, and adding new accounts;
  • the operation interfaces include but are not limited to: opening the uniform resource locator operation interface, the automatic login form operation interface, and the automatic login unified Resource locator operation interface, pop-up window operation interface.
  • Step S202 When the client receives the notification message of the registered message reminding event sent by the server, the client sends a return message of the message reminding event to the plug-in, and the plug-in displays the message reminding information according to the returned information.
  • the return information when the message reminding event includes receiving a new reminder, includes: an account identifier and an account information; when the message reminding event includes the account list being modified, the return information includes: an account identifier, an account information, and a number of new messages;
  • the account information includes at least one of the following: a display name, an avatar file, and signature information;
  • Step S203 When the client receives the operation request sent by the plug-in, the client invokes the registered operation interface and responds to the operation request.
  • the step includes: when the client receives the open uniform resource locator operation request sent by the plug-in, the client invokes the registered open resource locator operation interface. And opening a Uniform Resource Locator (URL, Uniform Resource Locator) in response to opening the Uniform Resource Locator operation request;
  • a Uniform Resource Locator URL, Uniform Resource Locator
  • the step specifically includes: when the client receives the automatic login form operation request sent by the plug-in, the client invokes the registered automatic login form operation interface and opens a new window, and loads a new window. Blank hypertext markup language information, fill in the form content into the hypertext markup language information and submit in response to the automatic login form operation request;
  • the step specifically includes: when the client receives the automatic login uniform resource locator operation request sent by the plug-in, the client invokes the registered automatic login uniform resource locator operation.
  • the interface automatically logs in to the uniform resource locator in response to the automatic login of the uniform resource locator operation request;
  • the step specifically includes: when the client receives the pop-up window request sent by the plug-in, the client invokes the registered pop-up operation interface and pops up the window in response to the pop-up request.
  • the second embodiment of the present application can receive the return information of such a message reminding event by the client when the new reminder, the account list is modified, the setting change, the new account is triggered, and the message reminding event is triggered. And send the return information to the appropriate plugin that registered for this type of message reminder event.
  • the system integration is improved, and the scalability of the program is further improved.
  • the message reminder program structure for receiving reminders such as new reminders, account list changes, setting changes, adding new accounts, etc., has little influence.
  • Example 1 the plugin includes an email reminder plugin
  • the email reminder plugin registers a message reminder event that receives a new reminder on the client, such as registering an OnMailReceived event, when the client detects an OnMailReceived event sent by the server.
  • the client sends the return information of the OnMailReceived event, such as the account ID AccountID and the account information AccountData, and the account number Count to the email reminder plugin; the email reminder plugin receives the new reminder message according to the return information of the OnMailReceived event.
  • Remind events to display such as display name, avatar file, signature information, etc.;
  • Example 2 the plugin includes a browser microblogging plugin
  • the browser's Weibo plugin is used to register the account list with the modified message reminder event, such as registering the OnSinaAccountChanged event.
  • the client detects the notification message of the OnSinaAccountChanged event sent by the server, the client will return the OnSinaAccountChanged event, such as an account.
  • the identifier, the account information, the number of new messages, and the number of accounts are sent to the browser microblog plug-in; the browser microblog plugin displays the message reminder event whose account list is modified according to the return information of the OnSinaAccountChanged event, and the account list is modified.
  • Account information of the account such as display name, avatar file, signature information, etc., and the number of new messages;
  • Example 3 the plugin includes a virtual machine desktop plugin
  • the guest plug-in of the virtual machine desktop registers the message reminder event of the setting change on the client, for example, registering the OnRenrenSettingChanged event.
  • the client detects the notification message of the OnRenrenSettingChanged event sent by the server, the client returns the information of the OnRenrenSettingChanged event - setting change
  • the information is sent to the plugin of the virtual machine desktop; the plugin is set according to the return information of the OnRenrenSettingChanged event, for example, the reminder only in the reminder message type list RemainType, the person plugin is set to only remind the fresh Things to show the corresponding news of the new things;
  • Example 4 the plugin includes the browser everyone plugin
  • the browser's everyone plug-in registers with the client to add a new account's message reminder event, such as registering the OnRenrenAccountAdded event.
  • a new account's message reminder event such as registering the OnRenrenAccountAdded event.
  • the client detects the notification message of the OnRenrenAccountAdded event sent by the server, the client will return the OnRenrenAccountAdded event, such as a new account.
  • the account ID and account information are sent to the browser plug-in; the guest plug-in displays the message reminder event of adding a new account according to the return information of the OnRenrenAccountAdded event, such as display name, avatar file, signature information and the like.
  • browser plug-ins can register to receive new reminders, account list changes, settings changes, add new accounts and other message reminders.
  • the events, the specific embodiments of the present application are not listed, but the application is not limited thereto.
  • the client uniformly provides an operation interface for opening a uniform resource locator operation interface, an automatic login form operation interface, an automatic login uniform resource locator operation interface, and a pop-up window operation interface.
  • the plug-in can save the corresponding interface.
  • the message reminder program framework for opening the interface of the uniform resource locator operation interface, the automatic login form operation interface, the automatic login uniform resource locator operation interface, and the pop-up window operation interface has little influence.
  • Example 1 after the plugin registers with the client to open the URL operation interface, the request for opening the URL is opened by calling the XML node OpenURL response plugin.
  • the OpenURL node includes: an action name OpenURL, a session identifier SessionID, and URL information, and may further include: account information and cookie information.
  • the client invokes the registered open URL operation interface, performs an action in the open URL operation interface, and feeds back the return value of the open URL operation to the caller of the client, such as a browser; wherein, the URL operation
  • the return value includes the FrameID of the URL, and the client returns the return value of the URL operation according to the caller's window handle feedback.
  • Example 2 After the plugin registers the automatic login form operation interface with the client, it responds to the plugin's automatic login form request by calling the XML node AutoLoginWebForm.
  • the AutoLoginWebForm node includes: an action name AutoLoginWebForm, a session identifier SessionID, an account name, and may also include: a form content, such as a special character of a CDATA field.
  • the client invokes the automatic login form operation interface, performs an action in the automatic login form operation interface, and feeds back the return value of the automatic login form operation to the caller of the client, such as a virtual machine desktop client;
  • the return value of the automatic login form operation includes the FrameID, and the client returns the return value of the automatic login form operation according to the caller's window handle.
  • Example 3 After the plugin registers the automatic login URL operation interface with the client, it responds to the plugin's automatic login URL request by calling the XML node AutoLoginURL.
  • AutoLoginURL node The method includes: an action name AutoLoginURL, a session identifier SessionID, and URL information, and may further include: a script code (JS) that needs to be executed in the URL.DocumentComplete event.
  • JS script code
  • the client invokes an automatic login URL operation interface, performs an action in the automatic login URL operation interface, and feeds back the return value of the automatic login URL operation to the caller of the client, such as a chat software client;
  • the return value of the automatic login form operation includes the FrameID where the URL is located, and the client returns the return value of the automatic login URL operation according to the caller's window handle.
  • Example 4 After the plug-in registers the automatic pop-up operation interface with the client, it responds to the plug-in automatic pop-up request by calling the XML node PopupWindow.
  • the PopupWindow node includes: an action name PopupWindow, a session identifier SessionID, and may also include: plug-in type data, such as information indicating the identity of the plug-in: mail, microblog, everyone, and the like.
  • the client invokes an automatic popup window operation interface, performs an action in the automatic popup window operation interface, and pops up the window in response to the plugin request.
  • the method of the second embodiment of the present application wherein the client has a sharing interface, the method further includes:
  • Step S204 When the plug-in issues the sharing information, the plug-in invokes the sharing interface, and distributes the sharing information to the network through the sharing interface;
  • the sharing information includes but is not limited to: text, a picture, a uniform resource locator, and an initialization file.
  • the initialization file includes: text, picture, title, sharing setting information, prompt information, and sharing success return information, which is file data containing more rich content.
  • the client can share the network information providing interface for the user, integrate the interface of the network sharing operation of the different plug-ins, and provide the interface of the network sharing operation through the client, thereby improving the program scalability of the sharing operation function. Moreover, the program architecture of network sharing operations has little impact.
  • the micro-blog plug-in can publish the micro-blog and other sharing information according to the user's network sharing operation, and the plug-in can publish the sharing information such as “new things” according to the user's network sharing operation.
  • the microblogging plugin Take the microblogging plugin as an example.
  • the microblogging plugin does not need to use the interface of its own plugin. It only needs to register the sharing interface on the client.
  • the microblogging plugin sends a request, and the client calls the client.
  • the sharing interface enables the user to complete the network sharing operation through the sharing interface of the client.
  • the "test1.ini” initialization file is parsed and sent to the network side through the client to complete the user's network sharing operation.
  • step 204 specifically includes: when the plugin issues the sharing information, the plugin invokes the sharing interface, and opens a new popup window overlying the sharing information input window of the plugin; when the popup window receives the sharing information input by the user When sharing, the shared information is posted to the network according to the type of plug-in.
  • the pop-up window of the client replaces the original sharing information input window of the plug-in, so that the pop-up window is suspended on the sharing information input window, thereby facilitating the user to input the result of the network sharing operation into the sharing interface of the client, instead of Enter the original interface to the plugin.
  • the client finds the handle of the plug-in sharing information input window, and the pop-up window is overlaid on the sharing information input window according to the handle.
  • the method of the second embodiment of the present application further includes:
  • Step S205 The plug-in cancels the message reminding event to the client, and is used to cancel the function of the client sending the return information of the message reminding event to the plug-in;
  • Step S206 The plug-in cancels the operation interface to the client, and is used to cancel the function of the client to invoke the operation interface.
  • the plug-in can be caused to cancel the message reminding event and the operation interface according to the operation of the user, and provide the user with various options.
  • FIG. 3 shows a flow chart of inter-process communication according to the second embodiment of the present application, as shown in FIG. 3, wherein the interaction between the plug-in and the client is through inter-process communication (IPC, Inter-Process). Communication) processing; in the process of inter-process communication, the plug-in is the sender and the client is the receiver, or the plug-in is the receiver and the client is the sender.
  • the steps of the inter-process communication include:
  • Step S231 the sender establishes a memory mapping file
  • Step S232 The sender writes the sending data to the memory mapping file.
  • Step S233 The sender sends a read message to the receiver.
  • Step S234 When the receiving party receives the read message, the receiver reads the sending data from the memory mapping file.
  • Step S235 The receiver sends a read completion message to the sender.
  • Step S236 When the sender receives the read completion message, the sender releases the memory map file.
  • the method of the second embodiment enables the client and the plug-in to directly access the shared data through the shared memory in the framework of the inter-process communication, thereby improving the communication efficiency between the plug-in and the client, and saving the system operation under the client-based message reminding mode. Resources, improve the speed of operation. The problem of waste of resources and low running speed caused by the client separately establishing a separate data storage area relative to the plug-in is avoided.
  • FIG. 4 is a structural diagram of a device for alerting a message according to a third embodiment of the present application. As shown in FIG. 4, it includes:
  • the registration module 100 is adapted to cause the plugin to register a message reminding event and an operation interface
  • the message reminding module 200 is adapted to send a return message of the message reminding event to the plug-in when receiving the notification message of the registered message reminding event sent by the server, and the plug-in displays the message reminding information according to the returned information;
  • the calling module 300 is adapted to invoke the registered operation interface to respond to the operation request when receiving the operation request sent by the plug-in.
  • the apparatus for message reminding provided by the third embodiment of the present application is the apparatus for implementing the message reminding method provided by the first embodiment of the present application, and the specific principle thereof is the same as the method for prompting the message provided by the first application of the present application. Therefore, it will not be repeated.
  • the device for message reminding provided by the third embodiment of the present application uniformly sends a reminder message from the server to each plug-in for processing, and provides a common operation interface for each plug-in to facilitate communication between the plug-in and the server, thereby solving the existing
  • the technical message reminder lacks scalability on the platform, which leads to the upgrade of complex problems.
  • the message reminder function needs to be upgraded, it is not necessary to upgrade for each plug-in, and only the client of the device can be upgraded.
  • the client-based message reminding method has little influence on the program architecture, and the program modification can be performed only on the client side of the device, and it is not necessary to change the program for each plug-in.
  • FIG. 5 is a structural diagram of a device for alerting a message according to a fourth embodiment of the present application. As shown in FIG. 5, it includes:
  • the registration module 100 is adapted to enable the plugin to register a message reminding event and an operation interface; the message reminding module 200. Suitable to send a return message of a message reminding event to the plug-in when receiving the notification message of the registered message reminding event sent by the server, the plug-in displaying the message reminding information according to the returned information; the calling module 300 is adapted to receive the plug-in When an operation request is sent, the registered operation interface is called to respond to the operation request.
  • the device of the fourth embodiment of the present application further includes: a startup module 400, specifically adapted to: start when the plug-in is started; or, when the caller starts, start; or, the plug-in queries a handle of the message window; The plugin starts when it does not query the handle of the message window.
  • a startup module 400 specifically adapted to: start when the plug-in is started; or, when the caller starts, start; or, the plug-in queries a handle of the message window; The plugin starts when it does not query the handle of the message window.
  • the apparatus of Embodiment 4 of the present application further includes: a broadcast module 500, configured to broadcast a registration request to each plug-in, so that each plug-in responds to the registration request and performs registration of the message reminding event and the operation interface.
  • a broadcast module 500 configured to broadcast a registration request to each plug-in, so that each plug-in responds to the registration request and performs registration of the message reminding event and the operation interface.
  • the device of the fourth embodiment of the present application further includes: a logout module 600, configured to: enable the plug-in to cancel the message reminding event, cancel the function of sending the return information of the message reminding event to the plug-in; and enable the plug-in to log out of the operation interface, Used to cancel the function of calling the operation interface.
  • a logout module 600 configured to: enable the plug-in to cancel the message reminding event, cancel the function of sending the return information of the message reminding event to the plug-in; and enable the plug-in to log out of the operation interface, Used to cancel the function of calling the operation interface.
  • the message reminding event includes but is not limited to: receiving a new reminder, modifying the account list, setting changes, and adding a new account.
  • the return information sent by the message reminding module 200 to the plug-in includes: an account identifier and account information; and when the message reminding event includes the account list being modified, the message reminding module 200 sends the return information to the plug-in.
  • the method includes: an account identifier, an account information, and a quantity of a new message; when the message reminding event includes a setting change, the return information sent by the message reminding module 200 to the plug-in includes: setting change information; when the message reminding event includes adding a new account, the message reminding
  • the return information sent by the module 200 to the plugin includes: an account ID and account information of the new account.
  • the operation interface comprises at least one of: opening a uniform resource locator operation interface, an automatic login form operation interface, an automatic login uniform resource locator operation interface, and a pop-up window operation interface;
  • the calling module 300 is specifically adapted to: when receiving the open uniform resource locator operation request sent by the plug-in, invoke the registered open unified resource locator operation interface and open the unified resource. a locator in response to opening a uniform resource locator operation request; when the operation interface includes an automatic login form operation interface, the calling module 300 has Suitable for: when receiving the automatic login form operation request sent by the plugin, call the registered automatic login form operation interface and open a new window, load a blank hypertext markup language information, fill the form content to the hypertext markup The language information is submitted and responded to the automatic login form operation request.
  • the calling module 300 is specifically adapted to: when receiving the automatic login uniform resource locator operation request sent by the plug-in Invoking the registered automatic login uniform resource locator operation interface and automatically logging in the uniform resource locator in response to the automatic login uniform resource locator operation request; when the operation interface includes a pop-up window operation interface, the calling module 300 is specifically adapted to: When receiving a pop-up request sent by the plug-in, the registered pop-up operation interface is called and a pop-up window is responded to in response to the pop-up request.
  • the device of Embodiment 4 of the present application further includes:
  • the sharing interface calling module 700 is adapted to enable the plug-in to invoke the sharing interface when the plug-in issues the sharing information, and distribute the sharing information to the network through the sharing interface;
  • the sharing information includes at least one of the following: a text, a picture, a uniform resource locator, and an initialization file. .
  • FIG. 6 is a detailed structural diagram of a device for alerting a message according to a fourth embodiment of the present application.
  • the sharing interface calling module 700 includes:
  • the pop-up window module 701 is adapted to enable the plug-in to invoke the sharing interface when the plug-in issues the sharing information, and open a new pop-up window overlying the sharing information input window of the plug-in;
  • the sharing publishing module 702 is adapted to receive when the pop-up window is received.
  • the device of Embodiment 4 of the present application further includes:
  • the inter-process communication module 800 is adapted to enable interaction between the plug-in and the device to be processed by inter-process communication; in the process of inter-process communication, the plug-in is a sender and the device is a receiver, or the plug-in is a receiver and the device is sent As shown in FIG. 6, the inter-process communication module 800 includes: a memory mapped file creating module 801, configured to enable a sender to establish a memory mapped file; and a memory mapped file writing module 802 adapted to cause the sender to write the transmitted data.
  • the read message sending module 803 is adapted to enable the sender to send the read message to the receiver;
  • the memory mapped file reading module 804 is adapted to cause the receiver to map from the memory when the receiving party receives the read message.
  • the reading completion message sending module 805 is adapted to enable the receiving party to send the reading completion message to the sender;
  • the memory mapping file releasing module 806 is adapted to enable the sending party to receive the reading completion message The sender releases the memory Shoot the file.
  • the apparatus for message reminding provided by the fourth embodiment of the present application is an apparatus for implementing the method for message reminding provided by the second embodiment of the present application, and the specific principle thereof is the same as the method for the method of message reminding provided by the second method of the present application. Therefore, it will not be repeated.
  • the device of the fourth embodiment of the present application can uniformly receive the return information of the message reminding event when the new reminder, the account list is modified, the setting change, the new account is triggered, and the message is returned, and the information is returned. Send to the appropriate plugin that registered this type of message reminder event.
  • the client of the device of the fourth embodiment of the present law unifies the message reminding event, the system integration degree is improved, and the scalability of the program is further improved.
  • the message reminder program structure for receiving reminders, such as new reminders, account list changes, setting changes, adding new accounts, etc. has little influence.
  • the apparatus of the fourth embodiment of the present application uniformly provides an operation interface for opening a uniform resource locator operation interface, an automatic login form operation interface, an automatic login uniform resource locator operation interface, a pop-up window operation interface, etc.
  • the system when the system is upgraded, only the client of the device in the fourth embodiment of the present application upgrades the corresponding interface, and no interface upgrade is required for each plug-in.
  • the message reminder program framework for opening the interface of the uniform resource locator operation interface, the automatic login form operation interface, the automatic login uniform resource locator operation interface, and the pop-up window operation interface has little influence.
  • FIG. 7 is a structural diagram of a system for message reminding according to the fifth embodiment of the present application.
  • the method includes:
  • the device 903 further includes: a plug-in module 901 and a server 902.
  • the plug-in module 901 is connected to the server 902 by the device for reminding the message of the third embodiment of the present application or the device for reminding the message of the fourth embodiment of the present application.
  • the message reminder device 903 includes a registration module 100, a message reminder module 200, and a call module 300.
  • a message alerting system provided by the fifth embodiment of the present application which mainly applies the message reminding device shown in FIG. 4, FIG. 5 or FIG. 6, the specific principle of the message alerting device and the device of the third embodiment of the present application or The specific principles of the apparatus of the fourth embodiment are the same, and therefore will not be described again.
  • the message reminding system uses a message reminding device to uniformly send a reminder message from the server to each plug-in module for processing, and to each plug-in module.
  • a universal operation interface is provided to facilitate communication between the plug-in module and the server, thereby solving the problem that the prior art message reminding method lacks scalability on the platform, thereby causing a complicated upgrade problem.
  • the message reminding function needs to be upgraded, it is not necessary to upgrade for each plug-in module, and only the client of the message reminding device of the fifth embodiment of the present application can be upgraded.
  • the message reminding method based on the client has little influence on the program architecture, and the program modification can be performed only on the client of the message reminding device, and it is not necessary to change the program of each plug-in module.
  • modules in the devices of the embodiments can be adaptively changed and placed in one or more devices different from the embodiment.
  • the modules or units or components of the embodiments may be combined into one module or unit or component, and further they may be divided into a plurality of sub-modules or sub-units or sub-components.
  • any combination of the features disclosed in the specification, including the accompanying claims, the abstract and the drawings, and any methods so disclosed, or All processes or units of the device are combined. Unless otherwise stated, this manual (including Each feature disclosed in the claims, the abstract and the drawings may be replaced by alternative features that provide the same, equivalent or similar purpose.
  • the various component embodiments of the present application can be implemented in hardware, or in a software module running on one or more processors, or in a combination thereof.
  • a microprocessor or digital signal processor may be used in practice to implement some or all of the functionality of some or all of the components of the message alerting in accordance with embodiments of the present application.
  • the application can also be implemented as a device or device program (e.g., a computer program and a computer program product) adapted to perform some or all of the methods described herein.
  • Such a program implementing the present application may be stored on a computer readable medium or may be in the form of one or more signals. Such signals may be downloaded from an Internet website, provided on a carrier signal, or provided in any other form.
  • Figure 8 illustrates a server, such as an application server, that can implement message reminders in accordance with the present application.
  • the server conventionally includes a processor 810 and a computer program product or computer readable medium in the form of a memory 820.
  • the memory 820 may be an electronic memory such as a flash memory, an EEPROM (Electrically Erasable Programmable Read Only Memory), an EPROM, a hard disk, or a ROM.
  • the memory 820 has a memory space 830 of program code 831 adapted to perform any of the method steps described above.
  • storage space 830 suitable for program code may include various program code 831 that are respectively adapted to implement various steps in the above methods.
  • the program code can be read from or written to one or more computer program products.
  • Such computer program products include program code carriers such as hard disks, compact disks (CDs), memory cards or floppy disks.
  • Such a computer program product is typically a portable or fixed storage unit as described with reference to FIG.
  • the storage unit may have a storage section, a storage space, and the like arranged similarly to the storage 820 in the server of FIG.
  • the program code can be compressed, for example, in an appropriate form.
  • the storage unit includes computer readable code 831', code that can be read by, for example, a processor such as 810, which The code, when run by the server, causes the server to perform the various steps in the methods described above.
  • "an embodiment," or "an embodiment," or "one or more embodiments" as used herein means that the particular features, structures, or characteristics described in connection with the embodiments are included in at least one embodiment of the present application.
  • phrase "in one embodiment" is not necessarily referring to the same embodiment.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

本申请公开了一种消息提醒的方法和装置、以及***，其中方法包括：插件向客户端注册消息提醒事件和操作接口；当所述客户端接收到服务器发送的已注册的所述消息提醒事件的通知消息时，所述客户端向所述插件发送所述消息提醒事件的返回信息，并且所述插件根据所述返回信息展现消息提醒信息；当所述客户端接收到所述插件发送的操作请求时，所述客户端调用已注册的所述操作接口，响应所述操作请求。本申请提供的一种消息提醒的方法和装置、以及***，解决了现有技术的消息提醒方式没有平台上的可扩展性，进而导致升级复杂的问题，取得了进一步提升消息提醒方式的程序扩展性的有益效果。

Description

一种消息提醒的方法和装置、以及*** 技术领域
本申请涉及互联网技术领域，具体涉及一种消息提醒的方法和装置、以及***。
背景技术
现有技术中，对于在网页应用或者网页内容的提醒机制，多是直接以插件的形式或者直接以功能项的方式集成在应用程序中；当终端设备接收到网页应用或网页变化的提醒消息时，通过应用程序编程接口(API，Application Programming Interface)，将提醒消息和数据直接发送至插件，由插件进行处理。上述插件包括微博插件、邮件提醒插件等。
例如，微博插件直接根据来自于服务器的提醒消息，对新微博数量、新关注的数量、新评论的数量等信息，在终端设备上进行显示，以提醒用户。
然而现有技术中的消息提醒是针对每个插件或者应用程序中的某一个功能项进行的，这种消息提醒方式没有平台上的可扩展性，进而导致升级复杂的问题，例如需要针对每个插件的消息提醒方式都进行修改、升级，才能满足要求，缺少程序上的扩展性。
发明内容
鉴于上述问题，提出了本申请以便提供一种克服上述问题或者至少部分地解决上述问题的消息提醒的方法和相应的消息提醒的装置、以及***。
根据本申请的第一个方面，提供了一种消息提醒的方法，其包括：插件向客户端注册消息提醒事件和操作接口；当客户端接收到服务器发送的已注册的消息提醒事件的通知消息时，客户端向插件发送消息提醒事件的返回信息，并且插件根据返回信息展现消息提醒信息；当客户端接收到插件发送的 操作请求时，客户端调用已注册的操作接口，响应操作请求。
根据本申请的第二个方面，提供了一种消息提醒的装置，其包括：注册模块，适于使插件注册消息提醒事件和操作接口；消息提醒模块，适于当接收到服务器发送的已注册的消息提醒事件的通知消息时，向插件发送消息提醒事件的返回信息，插件根据返回信息展现消息提醒信息；调用模块，适于当接收到插件发送的操作请求时，调用已注册的操作接口，响应操作请求。
根据本申请的第三个方面，提供了一种消息提醒的***，其包括：本申请消息提醒的装置，还包括：插件模块和服务器。
依据本发明的另一个方面，还提供了一种计算机程序，包括计算机可读代码，当所述计算机可读代码在计算机上运行时，将执行前述的消息提醒方法。
依据本发明的又一个方面，还提供了一种计算机可读介质，其中存储了前述的计算机程序。
根据本申请的一种消息提醒的方法和装置、以及***，通过在服务器和插件之间设有客户端，由客户端统一将来自服务器的提醒消息发送至各个插件进行处理，并且由客户端给各个插件提供通用的操作接口以便于插件与服务器沟通，由此解决了现有技术的消息提醒方式没有平台上的可扩展性，进而导致升级复杂的问题，取得了进一步提升消息提醒方式的程序扩展性的有益效果。
上述说明仅是本申请技术方案的概述，为了能够更清楚了解本申请的技术手段，而可依照说明书的内容予以实施，并且为了让本申请的上述和其它目的、特征和优点能够更明显易懂，以下特举本申请的具体实施方式。
附图说明
通过阅读下文优选实施方式的详细描述，各种其他的优点和益处对于本领域普通技术人员将变得清楚明了。附图仅用于示出优选实施方式的目的，而并不认为是对本申请的限制。而且在整个附图中，用相同的参考符号表示相同的部件。在附图中：
图1示出了根据本申请第一个实施例的消息提醒的方法流程图；
图2示出了根据本申请第二个实施例的消息提醒的方法流程图；
图3示出了根据本申请第二个实施例的进程间通信流程图；
图4示出了根据本申请第三个实施例的消息提醒的装置结构图；
图5示出了根据本申请第四个实施例的消息提醒的装置结构图；
图6示出了根据本申请第四个实施例的消息提醒的装置具体细化结构图；
图7示出了根据本申请第五个实施例的消息提醒的***结构图；
图8示意性地示出了用于执行根据本发明的方法的电子设备的框图；以及
图9示意性地示出了用于保持或者携带实现根据本发明的方法的程序代码的存储单元。
具体实施方式
下面将参照附图更详细地描述本公开的示例性实施例。虽然附图中显示了本公开的示例性实施例，然而应当理解，可以以各种形式实现本公开而不应被这里阐述的实施例所限制。相反，提供这些实施例是为了能够更透彻地理解本公开，并且能够将本公开的范围完整的传达给本领域的技术人员。
图1示出了根据本申请第一个实施例的消息提醒的方法流程图，如图1所示，该方法包括：
步骤S101、插件向客户端注册消息提醒事件和操作接口。
本申请中，插件指的是安装在终端设备的某个主程序中的起到一定补充功能的应用程序，其包括但不限于：浏览器的各种插件、聊天软件客户端插件、虚拟机桌面插件、邮件提醒插件以及其他具有消息提醒功能的插件。客户端是指在安装在终端设备中为客户提供本地服务的程序。这里终端设备可以包括：电子计算机、平板电脑、手机以及其它能够联网的设备。上述客户端受主程序的调用来工作，该主程序称为客户端的调用者，其包括但不限于：浏览器、聊天软件客户端、虚拟机桌面客户端或者邮件客户端，也就说上述 软件才拥有调用该客户端的权限。
步骤S102、当客户端接收到服务器发送的已注册的消息提醒事件的通知消息时，客户端向插件发送消息提醒事件的返回信息，并且插件根据返回信息展现消息提醒信息。
在服务器侧，当消息提醒事件被触发时，例如网页应用或网页数据发生变化时，服务器向终端设备发送通知消息以通知消息提醒事件被触发；当终端设备安装的客户端接收到通知消息时，客户端根据已注册的消息提醒事件判断是否是已注册的消息提醒事件的通知消息；如果是，说明已注册的消息提醒事件被触发，客户端将来自于服务器的该消息提醒事件的返回信息发送至注册该消息提醒事件的插件；而插件则根据返回信息展现消息提醒信息；展现消息提醒信息具体包括：显示消息提醒信息、弹出提醒窗口、调用声音文件以及其它能够引起用户注意的提醒方法。
步骤S103、当客户端接收到插件发送的操作请求时，客户端调用已注册的操作接口，响应操作请求。
当插件需要调用接口与服务器进行沟通时，插件不需要调用自身的接口，而是通过向客户端发送操作请求，通过客户端调用在客户端注册的由客户端提供的操作接口，进而与服务器进行沟通，完成用户基于插件的主动操作。
本申请第一个实施例的消息提醒的方法，通过在服务器和插件之间设有客户端，由客户端统一将来自服务器的提醒消息发送至各个插件进行处理，并且由客户端给各个插件提供通用的操作接口以便于插件与服务器沟通，由此解决了现有技术的消息提醒方式缺少平台上的可扩展性，进而导致升级复杂的问题。当需要对消息提醒功能进行升级时，不需要针对每个插件进行升级，仅对客户端进行升级即可。而且基于客户端的消息提醒方法对于程序构架影响很小，可以仅在客户端进行程序改动，不必对各个插件全都进行程序改动。
图2示出了根据本申请第二个实施例的消息提醒的方法流程图，如图2所示，在插件向客户端注册消息提醒事件和操作接口之前，需要首先启动客户端。具体地说，启动客户端可以有三种启动方式，分别为步骤S211、步骤S212和步骤S213。
步骤S211、在插件启动时，启动客户端；
步骤S212、在客户端的调用者启动时，启动客户端；
步骤S213、插件查询客户端的消息窗口的句柄；当插件没有查询到客户端的消息窗口的句柄时，启动客户端。
通过上述启动方式，能够在插件工作前，启动客户端，使插件通过客户端进行消息提醒的处理。上述三种启动方式主要说明启动客户端的时机，本申请不仅限于上述三种启动方式，也可以根据需求设定其它启动方式。
进一步的，在步骤S211、步骤S212或者步骤S213的启动客户端之后，本实施例的方法还包括：
步骤S221、客户端向各个插件广播发送注册请求，以便于各个插件响应注册请求并进行消息提醒事件和操作接口的注册。
通过上述广播方式，能够在启动客户端后，通过广播方式使插件注册消息提醒事件和操作接口，避免有插件被客户端遗漏。本申请插件向客户端注册消息提醒事件和操作接口不仅限基于上述广播方式。
步骤S201、插件向客户端注册消息提醒事件和操作接口。
其中消息提醒事件包括但不仅限于：收到新提醒、账号列表被修改、设置变更、添加新账号；操作接口包括但不仅限于：打开统一资源定位符操作接口、自动登录表单操作接口、自动登录统一资源定位符操作接口、弹出窗口操作接口。
步骤S202、当客户端接收到服务器发送的已注册的消息提醒事件的通知消息时，客户端向插件发送消息提醒事件的返回信息，并且插件根据返回信息展现消息提醒信息。
其中，当消息提醒事件包括收到新提醒时，返回信息包括：账号标识和账号信息；当消息提醒事件包括账号列表被修改时，返回信息包括：账号标识、账号信息和新消息的数量；当消息提醒事件包括设置变更时，返回信息包括：设置变更信息；当消息提醒事件包括添加新账号时，返回信息包括：新账号的账号标识和账号信息。
其中上述账号信息包括以下至少一个：显示名称、头像文件、签名信息；
步骤S203、当客户端接收到插件发送的操作请求时，客户端调用已注册的操作接口，响应操作请求。
其中，当操作接口包括打开统一资源定位符操作接口时，本步骤具体包括：当客户端接收到插件发送的打开统一资源定位符操作请求时，客户端调用已注册的打开统一资源定位符操作接口并打开统一资源定位符(URL，Uniform Resource Locator)，以响应打开统一资源定位符操作请求；
当操作接口包括自动登录表单操作接口时，本步骤具体包括：当客户端接收到插件发送的自动登录表单操作请求时，客户端调用已注册的自动登录表单操作接口并打开一个新窗口、加载一个空白的超文本标记语言信息、将表单内容填写至超文本标记语言信息内并提交，以响应自动登录表单操作请求；
当操作接口包括自动登录统一资源定位符操作接口时，本步骤具体包括：当客户端接收到插件发送的自动登录统一资源定位符操作请求时，客户端调用已注册的自动登录统一资源定位符操作接口并自动登录统一资源定位符，以响应自动登录统一资源定位符操作请求；
当操作接口包括弹出窗口操作接口时，本步骤具体包括：当客户端接收到插件发送的弹出窗口请求时，客户端调用已注册的弹出窗口操作接口并弹出窗口，以响应弹出窗口请求。
本申请第二个实施例通过上述技术方案，可以在收到新提醒、账号列表被修改、设置变更、添加新账号等消息提醒事件触发时，由客户端统一接收这类消息提醒事件的返回信息，并将返回信息发送至注册了这类消息提醒事件的相应插件。在客户端统一汇总消息提醒事件的情况下，提高***集成度，进一步提升程序的可扩展性。而且对于收到新提醒、账号列表被修改、设置变更、添加新账号等消息提醒事件的消息提醒程序构架影响很小。
下面通过几个具体的示例对插件注册消息提醒事件的方案进行介绍。
示例一，插件包括邮件提醒插件
邮件提醒插件在客户端注册收到新提醒的消息提醒事件，例如注册OnMailReceived事件，当客户端检测到服务器发送的OnMailReceived事件的 通知消息时，客户端将OnMailReceived事件的返回信息，例如账号标识AccountID和账号信息AccountData、以及账号数Count，发送至邮件提醒插件；邮件提醒插件则根据OnMailReceived事件的返回信息对收到新提醒的消息提醒事件进行展现，例如显示名称、头像文件、签名信息等信息；
示例二，插件包括浏览器微博插件
浏览器的微博插件在客户端注册账号列表被修改的消息提醒事件，例如注册OnSinaAccountChanged事件，当客户端检测到服务器发送的OnSinaAccountChanged事件的通知消息时，客户端将OnSinaAccountChanged事件的返回信息，例如账号标识、账号信息、新消息的数量以及账号数，发送至浏览器微博插件；浏览器微博插件则根据OnSinaAccountChanged事件的返回信息对账号列表被修改的消息提醒事件进行展现，展现账号列表被修改的账户的账号信息，例如显示名称、头像文件、签名信息等信息，以及新消息的数量；
示例三，插件包括虚拟机桌面插件
虚拟机桌面的人人插件在客户端注册设置变更的消息提醒事件，例如注册OnRenrenSettingChanged事件，当客户端检测到服务器发送的OnRenrenSettingChanged事件的通知消息时，客户端将OnRenrenSettingChanged事件的返回信息——设置变更信息发送至虚拟机桌面的人人插件；人人插件则根据OnRenrenSettingChanged事件的返回信息做出相应设置，例如对于提醒消息类型列表RemainType中的只提醒新鲜事设置，将人人插件设置为只提醒新鲜事，以进行相应的新鲜事消息展示；
示例四，插件包括浏览器人人插件
浏览器的人人插件在客户端注册添加新账号的消息提醒事件，例如注册OnRenrenAccountAdded事件，当客户端检测到服务器发送的OnRenrenAccountAdded事件的通知消息时，客户端将OnRenrenAccountAdded事件的返回信息，例如新账号的账号标识和账号信息，发送至浏览器人人插件；人人插件则根据OnRenrenAccountAdded事件的返回信息对添加新账号的消息提醒事件进行展现，例如显示名称、头像文件、签名信息等信息。
当然，浏览器插件、聊天软件客户端插件、虚拟机桌面插件、邮件提醒插件以及其他具有消息提醒功能的插件均可以注册收到新提醒、账号列表被修改、设置变更、添加新账号等消息提醒事件，本申请具体实施方式没有一一列明，但本申请并不以此为限制。
而且，本申请第二个实施例的消息提醒的方法，由客户端统一提供打开统一资源定位符操作接口、自动登录表单操作接口、自动登录统一资源定位符操作接口、弹出窗口操作接口等操作接口，一方面可以使插件省去相应接口，另一方面，在***升级时，仅在客户端升级相应接口即可，不需要针对每个插件进行接口升级。而且对于打开统一资源定位符操作接口、自动登录表单操作接口、自动登录统一资源定位符操作接口、弹出窗口操作接口等接口的消息提醒程序构架影响很小。
下面通过几个具体的示例对插件注册操作接口的方案进行介绍。
示例一，插件向客户端注册打开URL操作接口后，通过调用XML节点OpenURL响应插件打开URL的请求。OpenURL节点内包括：动作名称OpenURL、会话标识SessionID、URL信息，还可以包括：账号信息、Cookie信息。当插件请求打开URL时，客户端调用已注册的打开URL操作接口，执行打开URL操作接口内的动作，并且将打开URL操作的返回值反馈至客户端的调用者，例如浏览器；其中，URL操作的返回值包括URL的FrameID，客户端根据调用者的窗口句柄反馈打开URL操作的返回值。
示例二，插件向客户端注册自动登录表单操作接口后，通过调用XML节点AutoLoginWebForm以响应插件自动登录表单的请求。AutoLoginWebForm节点内包括：动作名称AutoLoginWebForm、会话标识SessionID、账号名称，还可以包括：表单内容，例如CDATA域的特殊字符等。当插件请求自动登录表单时，客户端调用自动登录表单操作接口，执行自动登录表单操作接口内的动作，并且将自动登录表单操作的返回值反馈至客户端的调用者，例如虚拟机桌面客户端；其中，自动登录表单操作的返回值包括FrameID，客户端根据调用者的窗口句柄反馈自动登录表单操作的返回值。
示例三，插件向客户端注册自动登录URL操作接口后，通过调用XML节点AutoLoginURL以响应插件自动登录URL的请求。AutoLoginURL节点 内包括：动作名称AutoLoginURL、会话标识SessionID、URL信息，还可以包括：在URL.DocumentComplete事件中需要执行的脚本代码(JS)。当插件请求自动URL时，客户端调用自动登录URL操作接口，执行自动登录URL操作接口内的动作，并且将自动登录URL操作的返回值反馈至客户端的调用者，例如聊天软件客户端；其中，自动登录表单操作的返回值包括URL所在的FrameID，客户端根据调用者的窗口句柄反馈自动登录URL操作的返回值。
示例四，插件向客户端注册自动弹出窗口操作接口后，通过调用XML节点PopupWindow以响应插件自动弹出窗口的请求。PopupWindow节点内包括：动作名称PopupWindow、会话标识SessionID，还可以包括：插件类型数据，例如表明插件身份的信息：邮件、微博、人人等。当插件请求自动弹出窗口时，客户端调用自动弹出窗口操作接口，执行自动弹出窗口操作接口内的动作，弹出窗口以响应插件的请求。
进一步的，本申请实施例二的方法，其中，客户端设有分享接口，方法还包括：
步骤S204、当插件发布分享信息时，插件调用分享接口，通过分享接口将分享信息发布至网络；分享信息包括但不限于：文字、图片、统一资源定位符、初始化文件。其中，初始化文件包括：文字、图片、标题、分享设置信息、提示信息、分享成功返回信息，是一种包含更加丰富内容的文件数据。
通过上述步骤S204，可以由客户端为用户分享网络信息提供接口，集成整合了不同插件的网络分享操作的接口，通过客户端提供网络分享操作的接口，能够提高分享操作功能的程序可扩展性。而且对于网络分享操作的程序构架影响很小。
例如，插件包括微博插件或者人人插件时，微博插件可以根据用户的网络分享操作发布微博等分享信息，人人插件可以根据用户的网络分享操作发布例如“新鲜事”的分享信息。以微博插件为例，微博插件不需要使用自身插件的接口，仅需要在客户端注册分享接口，进而当用户触发网络分享操作时，微博插件发送请求，由客户端调用客户端设有的分享接口，进而使用户通过客户端的分享接口完成网络分享操作。例如分享初始化文件采用：“Share：Ini＝C：\temp\test1.ini”，通过分享接口调用’C：\temp\”位置储存的 “test1.ini”初始化文件，进行解析并通过客户端发送至网络侧以完成用户的网络分享操作。
进一步的，上述步骤204具体包括：当插件发布分享信息时，插件调用分享接口，并打开一个新的覆盖于插件的分享信息输入窗口之上的弹出窗口；当弹出窗口接收到用户输入的分享信息时，通过分享接口将分享信息按照插件的类型发布至网络。
通过上述步骤，使客户端的弹出窗口代替插件原有的分享信息输入窗口，使弹出窗口悬浮于分享信息输入窗口之上，进而便于用户将网络分享操作的结果输入至客户端的分享接口中，而不是输入至插件的原有接口。客户端查找插件的分享信息输入窗口的句柄，根据句柄将弹出窗口覆盖于分享信息输入窗口之上。
进一步的，本申请实施例二的方法，其中，还包括：
步骤S205、插件向客户端注销消息提醒事件，用于取消客户端向插件发送消息提醒事件的返回信息的功能；
步骤S206、插件向客户端注销操作接口，用于取消客户端调用该操作接口的功能。
通过上述步骤S205和S206，可以使插件根据用户的操作注销消息提醒事件和操作接口，给用户提供多种选择。
进一步的，图3示出了根据本申请第二个实施例的进程间通信流程图，如图3所示，其中，插件和客户端之间的交互是通过进程间通信(IPC，Inter-Process Communication)进行处理；在进程间通信过程中，插件为发送方且客户端为接收方，或者，插件为接收方且客户端为发送方，进程间通信的步骤具体包括：
步骤S231、发送方建立内存映射文件；
步骤S232、发送方将发送数据写入内存映射文件；
步骤S233、发送方发送读取消息至接收方；
步骤S234、当接收方接收到读取消息时，接收方从内存映射文件中读取发送数据；
步骤S235、接收方发送读取完成消息至发送方；
步骤S236、当发送方接收到读取完成消息时，发送方释放内存映射文件。
实施例二的方法，使客户端和插件在进程间通信的框架下通过共享内存直接访问共享数据，能够提高插件和客户端之间的通信效率，节省了基于客户端的消息提醒方式下的***运行资源、提高了运行速度。避免了客户端相对于插件另外建立一个独立的数据存储区域带来的资源浪费、运行速度低下的问题。
图4示出了根据本申请第三个实施例的消息提醒的装置结构图，如图4所示，其包括：
注册模块100，适于使插件注册消息提醒事件和操作接口；
消息提醒模块200，适于当接收到服务器发送的已注册的消息提醒事件的通知消息时，向插件发送消息提醒事件的返回信息，插件根据返回信息展现消息提醒信息；
调用模块300，适于当接收到插件发送的操作请求时，调用已注册的操作接口，响应操作请求。
本申请的第三个实施例提供的消息提醒的装置，是本申请第一个实施例提供的消息提醒的方法的实现装置，其具体原理与本申请第一个提供的消息提醒的方法相同，因此不再赘述。
本申请第三个实施例提供的消息提醒的装置，统一将来自服务器的提醒消息发送至各个插件进行处理，并且给各个插件提供通用的操作接口以便于插件与服务器沟通，由此解决了现有技术的消息提醒方式缺少平台上的可扩展性，进而导致升级复杂的问题。当需要对消息提醒功能进行升级时，不需要针对每个插件进行升级，仅对本装置的客户端进行升级即可。而且基于客户端的消息提醒方法对于程序构架影响很小，可以仅在本装置的客户端进行程序改动，不必对各个插件全都进行程序改动。
图5示出了根据本申请第四个实施例的消息提醒的装置结构图，如图5所示，其包括：
注册模块100，适于使插件注册消息提醒事件和操作接口；消息提醒模块 200，适于当接收到服务器发送的已注册的消息提醒事件的通知消息时，向插件发送消息提醒事件的返回信息，插件根据返回信息展现消息提醒信息；调用模块300，适于当接收到插件发送的操作请求时，调用已注册的操作接口，响应操作请求。
进一步的，本申请实施例四的装置还包括：启动模块400，具体适于：在插件启动时，进行启动；或者，在调用者启动时，进行启动；或者，插件查询消息窗口的句柄；当插件没有查询到消息窗口的句柄时，进行启动。
进一步的，本申请实施例四的装置还包括：广播模块500，适于向各个插件广播发送注册请求，以便于各个插件响应注册请求并进行消息提醒事件和操作接口的注册。
进一步的，本申请实施例四的装置还包括：注销模块600，适于：使插件注销消息提醒事件，用以取消向插件发送消息提醒事件的返回信息的功能；以及，使插件注销操作接口，用以取消调用该操作接口的功能。
进一步的，消息提醒事件包括但不限于：收到新提醒、账号列表被修改、设置变更、添加新账号。
当消息提醒事件包括收到新提醒时，消息提醒模块200向插件发送的返回信息包括：账号标识和账号信息；当消息提醒事件包括账号列表被修改时，消息提醒模块200向插件发送的返回信息包括：账号标识、账号信息和新消息的数量；当消息提醒事件包括设置变更时，消息提醒模块200向插件发送的返回信息包括：设置变更信息；当消息提醒事件包括添加新账号时，消息提醒模块200向插件发送的返回信息包括：新账号的账号标识和账号信息。
进一步的，本申请实施例四的装置，其中，操作接口包括以下至少一个：打开统一资源定位符操作接口、自动登录表单操作接口、自动登录统一资源定位符操作接口、弹出窗口操作接口；
当操作接口包括打开统一资源定位符操作接口时，调用模块300具体适于：当接收到插件发送的打开统一资源定位符操作请求时，调用已注册的打开统一资源定位符操作接口并打开统一资源定位符，以响应打开统一资源定位符操作请求；当操作接口包括自动登录表单操作接口时，调用模块300具 体适于：当接收到插件发送的自动登录表单操作请求时，调用已注册的自动登录表单操作接口并打开一个新窗口、加载一个空白的超文本标记语言信息、将表单内容填写至超文本标记语言信息内并提交，以响应自动登录表单操作请求；当操作接口包括自动登录统一资源定位符操作接口时，调用模块300具体适于：当接收到插件发送的自动登录统一资源定位符操作请求时，调用已注册的自动登录统一资源定位符操作接口并自动登录统一资源定位符，以响应自动登录统一资源定位符操作请求；当操作接口包括弹出窗口操作接口时，调用模块300具体适于：当接收到插件发送的弹出窗口请求时，调用已注册的弹出窗口操作接口并弹出窗口，以响应弹出窗口请求。
进一步的，本申请实施例四的装置，其中，还包括：
分享接口调用模块700，适于当插件发布分享信息时，使插件调用分享接口，通过分享接口将分享信息发布至网络；分享信息包括以下至少之一：文字、图片、统一资源定位符、初始化文件。
图6示出了根据本申请第四个实施例的消息提醒的装置具体细化结构图，如图6所示，其中，分享接口调用模块700包括：
弹出窗口模块701，适于当插件发布分享信息时，使插件调用分享接口，并打开一个新的覆盖于插件的分享信息输入窗口之上的弹出窗口；分享发布模块702，适于当弹出窗口接收到用户输入的分享信息时，通过分享接口将分享信息按照插件的类型发布至网络。
进一步的，本申请实施例四的装置，其中，还包括：
进程间通信模块800，适于使插件和装置之间的交互通过进程间通信进行处理；在进程间通信过程中，插件为发送方且装置为接收方，或者，插件为接收方且装置为发送方，如图6所示，进程间通信模块800包括：内存映射文件建立模块801，适于使发送方建立内存映射文件；内存映射文件写入模块802，适于使发送方将发送数据写入内存映射文件；读取消息发送模块803，适于使发送方发送读取消息至接收方；内存映射文件读取模块804，适于当接收方接收到读取消息时，使接收方从内存映射文件中读取发送数据；读取完成消息发送模块805，适于使接收方发送读取完成消息至发送方；内存映射文件释放模块806，适于当发送方接收到读取完成消息时，使发送方释放内存映 射文件。
本申请的第四个实施例提供的消息提醒的装置，是本申请第二个提供的消息提醒的方法的实现装置，其具体原理与本申请第二个提供的消息提醒的方法的原理相同，因此不再赘述。
本申请第四个实施例的装置，可以在收到新提醒、账号列表被修改、设置变更、添加新账号等消息提醒事件触发时，统一接收这类消息提醒事件的返回信息，并将返回信息发送至注册了这类消息提醒事件的相应插件。在本法名实施例四的装置的客户端统一汇总消息提醒事件的情况下，提高***集成度，进一步提升程序的可扩展性。而且对于收到新提醒、账号列表被修改、设置变更、添加新账号等消息提醒事件的消息提醒程序构架影响很小。
而且，本申请第四个实施例的装置，统一提供打开统一资源定位符操作接口、自动登录表单操作接口、自动登录统一资源定位符操作接口、弹出窗口操作接口等操作接口，一方面可以使插件省去相应接口，另一方面，在***升级时，仅在本申请实施例四的装置的客户端升级相应接口即可，不需要针对每个插件进行接口升级。而且对于打开统一资源定位符操作接口、自动登录表单操作接口、自动登录统一资源定位符操作接口、弹出窗口操作接口等接口的消息提醒程序构架影响很小。
本申请第五个实施例提供了一种消息提醒的***，图7示出了根据本申请第五个实施例的消息提醒的***结构图，如图7所示，其包括：本申请消息提醒的装置903，还包括：插件模块901和服务器902。
插件模块901通过本申请实施例三的消息提醒的装置或者本申请实施例四的消息提醒的装置，连接至服务器902。消息提醒的装置903包括注册模块100、消息提醒模块200和调用模块300。
本申请的第五个实施例提供的消息提醒的***，其主要应用图4、图5或者图6示出的消息提醒装置，消息提醒装置的具体原理与本申请第三个实施例的装置或者第四个实施例的装置的具体原理相同，因此不再赘述。
本申请第五个实施例提供的消息提醒的***，利用消息提醒装置统一将来自服务器的提醒消息发送至各个插件模块进行处理，并且给各个插件模块 提供通用的操作接口以便于插件模块与服务器沟通，由此解决了现有技术的消息提醒方式缺少平台上的可扩展性，进而导致升级复杂的问题。当需要对消息提醒功能进行升级时，不需要针对每个插件模块进行升级，仅对本申请实施例五的消息提醒装置的客户端进行升级即可。而且基于客户端的消息提醒方法对于程序构架影响很小，可以仅在消息提醒装置的客户端进行程序改动，不必对各个插件模块全都进行程序改动。
在此提供的算法和显示不与任何特定计算机、虚拟***或者其它设备固有相关。各种通用***也可以与基于在此的示教一起使用。根据上面的描述，构造这类***所要求的结构是显而易见的。此外，本申请也不针对任何特定编程语言。应当明白，可以利用各种编程语言实现在此描述的本申请的内容，并且上面对特定语言所做的描述是为了披露本申请的最佳实施方式。
在此处所提供的说明书中，说明了大量具体细节。然而，能够理解，本申请的实施例可以在没有这些具体细节的情况下实践。在一些实例中，并未详细示出公知的方法、结构和技术，以便不模糊对本说明书的理解。
类似地，应当理解，为了精简本公开并帮助理解各个发明方面中的一个或多个，在上面对本申请的示例性实施例的描述中，本申请的各个特征有时被一起分组到单个实施例、图、或者对其的描述中。然而，并不应将该公开的方法解释成反映如下意图：即所要求保护的本申请要求比在每个权利要求中所明确记载的特征更多的特征。更确切地说，如下面的权利要求书所反映的那样，发明方面在于少于前面公开的单个实施例的所有特征。因此，遵循具体实施方式的权利要求书由此明确地并入该具体实施方式，其中每个权利要求本身都作为本申请的单独实施例。
本领域那些技术人员可以理解，可以对实施例中的设备中的模块进行自适应性地改变并且把它们设置在与该实施例不同的一个或多个设备中。可以把实施例中的模块或单元或组件组合成一个模块或单元或组件，以及此外可以把它们分成多个子模块或子单元或子组件。除了这样的特征和/或过程或者单元中的至少一些是相互排斥之外，可以采用任何组合对本说明书(包括伴随的权利要求、摘要和附图)中公开的所有特征以及如此公开的任何方法或者设备的所有过程或单元进行组合。除非另外明确陈述，本说明书(包括伴 随的权利要求、摘要和附图)中公开的每个特征可以由提供相同、等同或相似目的的替代特征来代替。
此外，本领域的技术人员能够理解，尽管在此所述的一些实施例包括其它实施例中所包括的某些特征而不是其它特征，但是不同实施例的特征的组合意味着处于本申请的范围之内并且形成不同的实施例。例如，在下面的权利要求书中，所要求保护的实施例的任意之一都可以以任意的组合方式来使用。
本申请的各个部件实施例可以以硬件实现，或者以在一个或者多个处理器上运行的软件模块实现，或者以它们的组合实现。本领域的技术人员应当理解，可以在实践中使用微处理器或者数字信号处理器(DSP)来实现根据本申请实施例的消息提醒的装置中的一些或者全部部件的一些或者全部功能。本申请还可以实现为适于执行这里所描述的方法的一部分或者全部的设备或者装置程序(例如，计算机程序和计算机程序产品)。这样的实现本申请的程序可以存储在计算机可读介质上，或者可以具有一个或者多个信号的形式。这样的信号可以从因特网网站上下载得到，或者在载体信号上提供，或者以任何其他形式提供。
例如，图8示出了可以实现根据本申请的消息提醒的服务器，例如应用服务器。该服务器传统上包括处理器810和以存储器820形式的计算机程序产品或者计算机可读介质。存储器820可以是诸如闪存、EEPROM(电可擦除可编程只读存储器)、EPROM、硬盘或者ROM之类的电子存储器。存储器820具有适于执行上述方法中的任何方法步骤的程序代码831的存储空间830。例如，适于程序代码的存储空间830可以包括分别适于实现上面的方法中的各种步骤的各个程序代码831。这些程序代码可以从一个或者多个计算机程序产品中读出或者写入到这一个或者多个计算机程序产品中。这些计算机程序产品包括诸如硬盘，紧致盘(CD)、存储卡或者软盘之类的程序代码载体。这样的计算机程序产品通常为如参考图9所述的便携式或者固定存储单元。该存储单元可以具有与图8的服务器中的存储器820类似布置的存储段、存储空间等。程序代码可以例如以适当形式进行压缩。通常，存储单元包括计算机可读代码831’，即可以由例如诸如810之类的处理器读取的代码，这 些代码当由服务器运行时，导致该服务器执行上面所描述的方法中的各个步骤。
本文中所称的“一个实施例”、“实施例”或者“一个或者多个实施例”意味着，结合实施例描述的特定特征、结构或者特性包括在本申请的至少一个实施例中。此外，请注意，这里“在一个实施例中”的词语例子不一定全指同一个实施例。
在此处所提供的说明书中，说明了大量具体细节。然而，能够理解，本申请的实施例可以在没有这些具体细节的情况下被实践。在一些实例中，并未详细示出公知的方法、结构和技术，以便不模糊对本说明书的理解。
应该注意的是上述实施例对本申请进行说明而不是对本申请进行限制，并且本领域技术人员在不脱离所附权利要求的范围的情况下可设计出替换实施例。在权利要求中，不应将位于括号之间的任何参考符号构造成对权利要求的限制。单词“包含”不排除存在未列在权利要求中的元件或步骤。位于元件之前的单词“一”或“一个”不排除存在多个这样的元件。本申请可以借助于包括有若干不同元件的硬件以及借助于适当编程的计算机来实现。在列举了若干装置的单元权利要求中，这些装置中的若干个可以是通过同一个硬件项来具体体现。单词第一、第二、以及第三等的使用不表示任何顺序。可将这些单词解释为名称。

Claims (21)

  1. 一种消息提醒的方法，其包括：
    插件向客户端注册消息提醒事件和操作接口；
    当所述客户端接收到服务器发送的已注册的所述消息提醒事件的通知消息时，所述客户端向所述插件发送所述消息提醒事件的返回信息，并且所述插件根据所述返回信息展现消息提醒信息；
    当所述客户端接收到所述插件发送的操作请求时，所述客户端调用已注册的所述操作接口，响应所述操作请求。
  2. 根据权利要求1所述的方法，其中，所述插件向客户端注册消息提醒事件和操作接口之前，还包括：
    在所述插件启动时，启动所述客户端；
    或者，在所述客户端的调用者启动时，启动所述客户端；
    或者，所述插件查询所述客户端的消息窗口的句柄；当所述插件没有查询到所述客户端的消息窗口的句柄时，启动所述客户端。
  3. 根据权利要求2所述的方法，其中，在所述启动客户端之后，所述客户端向各个所述插件广播发送注册请求，以便于各个所述插件响应所述注册请求并进行所述消息提醒事件和所述操作接口的注册。
  4. 根据权利要求1所述的方法，其中，还包括：
    插件向客户端注销消息提醒事件，用于取消所述客户端向所述插件发送所述消息提醒事件的返回信息的功能；
    插件向客户端注销操作接口，用于取消客户端调用该操作接口的功能。
  5. 根据权利要求1所述的方法，其中，所述消息提醒事件包括以下至少一个：收到新提醒、账号列表被修改、设置变更、添加新账号；
    当所述消息提醒事件包括所述收到新提醒时，所述返回信息包括：账号标识和账号信息；
    当所述消息提醒事件包括所述账号列表被修改时，所述返回信息包括：账号标识、账号信息和新消息的数量；
    当所述消息提醒事件包括所述设置变更时，所述返回信息包括：设置变更信息；
    当所述消息提醒事件包括所述添加新账号时，所述返回信息包括：新账号的账号标识和账号信息。
  6. 根据权利要求1所述的方法，其中，所述操作接口包括以下至少一个：打开统一资源定位符操作接口、自动登录表单操作接口、自动登录统一资源定位符操作接口、弹出窗口操作接口；
    当所述操作接口包括所述打开统一资源定位符操作接口时，所述当客户端接收到所述插件发送的操作请求时，所述客户端调用已注册的所述操作接口，响应所述操作请求的步骤具体包括：当所述客户端接收到所述插件发送的打开统一资源定位符操作请求时，所述客户端调用已注册的所述打开统一资源定位符操作接口并打开统一资源定位符，以响应所述打开统一资源定位符操作请求；
    当所述操作接口包括所述自动登录表单操作接口时，所述当所述客户端接收到所述插件发送的操作请求时，所述客户端调用已注册的所述操作接口，响应所述操作请求的步骤具体包括：当所述客户端接收到所述插件发送的自动登录表单操作请求时，所述客户端调用已注册的所述自动登录表单操作接口并打开一个新窗口、加载一个空白的超文本标记语言信息、将表单内容填写至所述超文本标记语言信息内并提交，以响应所述自动登录表单操作请求；
    当所述操作接口包括所述自动登录统一资源定位符操作接口时，所述当所述客户端接收到所述插件发送的操作请求时，所述客户端调用已注册的所述操作接口，响应所述操作请求的步骤具体包括：当所述客户端接收到所述插件发送的自动登录统一资源定位符操作请求时，所述客户端调用已注册的所述自动登录统一资源定位符操作接口并自动登录统一资源定位符，以响应所述自动登录统一资源定位符操作请求；
    当所述操作接口包括所述弹出窗口操作接口时，所述当所述客户端接收到所述插件发送的操作请求时，所述客户端调用已注册的所述操作接口，响应所述操作请求的步骤具体包括：当所述客户端接收到所述插件发送的弹出窗口请求时，所述客户端调用已注册的所述弹出窗口操作接口并弹出窗口， 以响应所述弹出窗口请求。
  7. 根据权利要求1所述的方法，其中，所述客户端设有分享接口，所述方法还包括：
    当所述插件发布分享信息时，所述插件调用所述分享接口，通过所述分享接口将所述分享信息发布至网络；所述分享信息包括以下至少之一：文字、图片、统一资源定位符、初始化文件。
  8. 根据权利要求7所述的方法，其中，当所述插件发布分享信息时，所述插件调用所述分享接口，通过所述分享接口将所述分享信息发布至网络的步骤具体包括：
    当所述插件发布所述分享信息时，所述插件调用所述分享接口，并打开一个新的覆盖于所述插件的分享信息输入窗口之上的弹出窗口；
    当所述弹出窗口接收到用户输入的所述分享信息时，通过所述分享接口将所述分享信息按照所述插件的类型发布至网络。
  9. 根据权利要求1～8任一项所述的方法，其中，所述插件和所述客户端之间的交互是通过进程间通信进行处理；在所述进程间通信过程中，所述插件为发送方且所述客户端为接收方，或者，所述插件为接收方且所述客户端为发送方，所述进程间通信的步骤具体包括：
    所述发送方建立内存映射文件；
    所述发送方将发送数据写入所述内存映射文件；
    所述发送方发送读取消息至所述接收方；
    当所述接收方接收到所述读取消息时，所述接收方从所述内存映射文件中读取所述发送数据；
    所述接收方发送读取完成消息至所述发送方；
    当所述发送方接收到所述读取完成消息时，所述发送方释放所述内存映射文件。
  10. 一种消息提醒的装置，其包括：
    注册模块，适于使插件注册消息提醒事件和操作接口；
    消息提醒模块，适于当接收到服务器发送的已注册的所述消息提醒事件的通知消息时，向所述插件发送所述消息提醒事件的返回信息，所述插件根据所述返回信息展现消息提醒信息；
    调用模块，适于当接收到所述插件发送的操作请求时，调用已注册的所述操作接口，响应所述操作请求。
  11. 根据权利要求10所述的装置，其中，还包括：启动模块，具体适于：
    在所述插件启动时，进行启动；
    或者，在调用者启动时，进行启动；
    或者，所述插件查询消息窗口的句柄；当所述插件没有查询到消息窗口的句柄时，进行启动。
  12. 根据权利要求11所述的装置，其中，还包括：
    广播模块，适于向各个所述插件广播发送注册请求，以便于各个所述插件响应所述注册请求并进行所述消息提醒事件和所述操作接口的注册。
  13. 根据权利要求10所述的装置，其中，还包括：注销模块，适于：使插件注销消息提醒事件，用以取消向所述插件发送所述消息提醒事件的返回信息的功能；以及，使插件注销操作接口，用以取消调用该操作接口的功能。
  14. 根据权利要求10所述的装置，其中，所述消息提醒事件包括以下至少一个：收到新提醒、账号列表被修改、设置变更、添加新账号；
    当所述消息提醒事件包括所述收到新提醒时，所述消息提醒模块向所述插件发送的所述返回信息包括：账号标识和账号信息；
    当所述消息提醒事件包括所述账号列表被修改时，所述消息提醒模块向所述插件发送的所述返回信息包括：账号标识、账号信息和新消息的数量；
    当所述消息提醒事件包括所述设置变更时，所述消息提醒模块向所述插件发送的所述返回信息包括：设置变更信息；
    当所述消息提醒事件包括所述添加新账号时，所述消息提醒模块向所述插件发送的所述返回信息包括：新账号的账号标识和账号信息。
  15. 根据权利要求10所述的装置，其中，所述操作接口包括以下至少一 个：打开统一资源定位符操作接口、自动登录表单操作接口、自动登录统一资源定位符操作接口、弹出窗口操作接口；
    当所述操作接口包括所述打开统一资源定位符操作接口时，所述调用模块具体适于：当接收到所述插件发送的打开统一资源定位符操作请求时，调用已注册的所述打开统一资源定位符操作接口并打开统一资源定位符，以响应所述打开统一资源定位符操作请求；
    当所述操作接口包括所述自动登录表单操作接口时，所述调用模块具体适于：当接收到所述插件发送的自动登录表单操作请求时，调用已注册的所述自动登录表单操作接口并打开一个新窗口、加载一个空白的超文本标记语言信息、将表单内容填写至所述超文本标记语言信息内并提交，以响应所述自动登录表单操作请求；
    当所述操作接口包括所述自动登录统一资源定位符操作接口时，所述调用模块具体适于：当接收到所述插件发送的自动登录统一资源定位符操作请求时，调用已注册的所述自动登录统一资源定位符操作接口并自动登录统一资源定位符，以响应所述自动登录统一资源定位符操作请求；
    当所述操作接口包括所述弹出窗口操作接口时，所述调用模块具体适于：当接收到所述插件发送的弹出窗口请求时，调用已注册的所述弹出窗口操作接口并弹出窗口，以响应所述弹出窗口请求。
  16. 根据权利要求10所述的装置，其中，还包括：
    分享接口调用模块，适于当所述插件发布分享信息时，使所述插件调用分享接口，通过所述分享接口将所述分享信息发布至网络；所述分享信息包括以下至少之一：文字、图片、统一资源定位符、初始化文件。
  17. 根据权利要求16所述的装置，其中，所述分享接口调用模块包括：
    弹出窗口模块，适于当所述插件发布所述分享信息时，使所述插件调用所述分享接口，并打开一个新的覆盖于所述插件的分享信息输入窗口之上的弹出窗口；
    分享发布模块，适于当所述弹出窗口接收到用户输入的所述分享信息时，通过所述分享接口将所述分享信息按照所述插件的类型发布至网络。
  18. 根据权利要求10～16任一项所述的装置，其中，还包括：
    进程间通信模块，适于使所述插件和所述装置之间的交互通过进程间通信进行处理；在所述进程间通信过程中，所述插件为发送方且所述装置为接收方，或者，所述插件为接收方且所述装置为发送方，所述进程间通信模块包括：
    内存映射文件建立模块，适于使所述发送方建立内存映射文件；
    内存映射文件写入模块，适于使所述发送方将发送数据写入所述内存映射文件；
    读取消息发送模块，适于使所述发送方发送读取消息至所述接收方；
    内存映射文件读取模块，适于当所述接收方接收到所述读取消息时，使所述接收方从所述内存映射文件中读取所述发送数据；
    读取完成消息发送模块，适于使所述接收方发送读取完成消息至所述发送方；
    内存映射文件释放模块，适于当所述发送方接收到所述读取完成消息时，使所述发送方释放所述内存映射文件。
  19. 一种消息提醒的***，其包括：权利要求10～18任一项所述的装置，还包括：插件模块和服务器。
  20. 一种计算机程序，包括计算机可读代码，当所述计算机可读代码在电子设备上运行时，导致所述电子设备执行根据权利要求1-9中的任一个所述的消息提醒方法。
  21. 一种计算机可读介质，其中存储了如权利要求20所述的计算机程序。
PCT/CN2014/087279 2013-10-18 2014-09-24 一种消息提醒的方法和装置、以及*** WO2015055073A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201310492698.9 2013-10-18
CN201310492698.9A CN103516595B (zh) 2013-10-18 2013-10-18 一种消息提醒的方法和装置、以及***

Publications (1)

Publication Number Publication Date
WO2015055073A1 true WO2015055073A1 (zh) 2015-04-23

Family

ID=49898667

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/087279 WO2015055073A1 (zh) 2013-10-18 2014-09-24 一种消息提醒的方法和装置、以及***

Country Status (2)

Country Link
CN (1) CN103516595B (zh)
WO (1) WO2015055073A1 (zh)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111124529A (zh) * 2019-11-21 2020-05-08 杭州米络星科技(集团)有限公司 一种基于浏览器ppapi插件技术的视频投屏方法
CN111857985A (zh) * 2020-06-08 2020-10-30 远光软件股份有限公司 浏览器插件的调用方法、装置、存储介质及终端
CN113076294A (zh) * 2021-04-16 2021-07-06 北京沃东天骏信息技术有限公司 一种信息分享方法和装置
CN113760569A (zh) * 2021-01-06 2021-12-07 北京沃东天骏信息技术有限公司 一种多账号管理方法和***
CN115297162A (zh) * 2022-06-27 2022-11-04 青岛海尔科技有限公司 消息的发送方法和装置、存储介质及电子装置

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103516595B (zh) * 2013-10-18 2016-11-09 北京奇虎科技有限公司 一种消息提醒的方法和装置、以及***
CN104462313B (zh) * 2014-11-28 2018-04-13 北京奇虎科技有限公司 一种数据处理中的监控方法和装置
CN105991410B (zh) * 2015-02-12 2020-06-30 北京创新方舟科技有限公司 一种获取消息的方法和***
CN105262717A (zh) * 2015-08-31 2016-01-20 福建天晴数码有限公司 一种网络服务安全管理方法及装置
CN108345621B (zh) * 2017-01-24 2022-03-08 腾讯科技（深圳）有限公司 一种数据对账方法、***及数据***
CN112269655B (zh) * 2020-10-15 2023-01-13 北京百度网讯科技有限公司 内存映射文件清理方法、装置、电子设备及存储介质
CN113094188A (zh) * 2021-03-30 2021-07-09 网易（杭州）网络有限公司 ***消息的处理方法及装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100293491A1 (en) * 2009-05-12 2010-11-18 Ricoh Company, Ltd. Information Processing Apparatus, System, And Program
CN103164239A (zh) * 2012-12-11 2013-06-19 广东电网公司电力科学研究院 基于微网可视化平台的插件实现方法
CN103176789A (zh) * 2011-12-26 2013-06-26 腾讯科技（深圳）有限公司 一种实现开放平台功能扩展的方法及***
CN103268319A (zh) * 2013-04-17 2013-08-28 北京航空航天大学 一种基于网页的云浏览器
CN103516595A (zh) * 2013-10-18 2014-01-15 北京奇虎科技有限公司 一种消息提醒的方法和装置、以及***

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9083663B2 (en) * 2006-02-04 2015-07-14 Docsof, Llc Reminder system
CN101847100B (zh) * 2010-06-08 2012-12-05 用友软件股份有限公司 扩展软件应用的方法和装置
CN103309700B (zh) * 2012-03-16 2016-05-18 腾讯科技（深圳）有限公司 一种插件管理控制方法及装置
CN103034721A (zh) * 2012-12-13 2013-04-10 北京奇虎科技有限公司 一种消息展示客户端及展示方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100293491A1 (en) * 2009-05-12 2010-11-18 Ricoh Company, Ltd. Information Processing Apparatus, System, And Program
CN103176789A (zh) * 2011-12-26 2013-06-26 腾讯科技（深圳）有限公司 一种实现开放平台功能扩展的方法及***
CN103164239A (zh) * 2012-12-11 2013-06-19 广东电网公司电力科学研究院 基于微网可视化平台的插件实现方法
CN103268319A (zh) * 2013-04-17 2013-08-28 北京航空航天大学 一种基于网页的云浏览器
CN103516595A (zh) * 2013-10-18 2014-01-15 北京奇虎科技有限公司 一种消息提醒的方法和装置、以及***

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111124529A (zh) * 2019-11-21 2020-05-08 杭州米络星科技(集团)有限公司 一种基于浏览器ppapi插件技术的视频投屏方法
CN111857985A (zh) * 2020-06-08 2020-10-30 远光软件股份有限公司 浏览器插件的调用方法、装置、存储介质及终端
CN113760569A (zh) * 2021-01-06 2021-12-07 北京沃东天骏信息技术有限公司 一种多账号管理方法和***
CN113760569B (zh) * 2021-01-06 2024-04-05 北京沃东天骏信息技术有限公司 一种多账号管理方法和***
CN113076294A (zh) * 2021-04-16 2021-07-06 北京沃东天骏信息技术有限公司 一种信息分享方法和装置
CN115297162A (zh) * 2022-06-27 2022-11-04 青岛海尔科技有限公司 消息的发送方法和装置、存储介质及电子装置
CN115297162B (zh) * 2022-06-27 2024-03-22 青岛海尔科技有限公司 消息的发送方法和装置、存储介质及电子装置

Also Published As

Publication number Publication date
CN103516595B (zh) 2016-11-09
CN103516595A (zh) 2014-01-15

Similar Documents

Publication Publication Date Title
WO2015055073A1 (zh) 一种消息提醒的方法和装置、以及***
JP6955074B2 (ja) メッセージング・ボット・リッチ・コミュニケーションのための技法
JP6615269B2 (ja) モバイル・プッシュ通知
US8751575B2 (en) System and method for generating a ghost profile for a social network
JP2021144722A (ja) メッセージングエージェントプラットフォームのための技術
US9274913B2 (en) Event pages for web applications and extensions
US8849957B1 (en) Installable web applications
US9754326B2 (en) Aggregate provider for social activity feeds and contact information
US9009853B2 (en) Communication between web applications
JP6903739B2 (ja) アプリケーション内でサードパーティ・サービスにアクセスするための方法およびシステム
MX2013007842A (es) Mejoras para el cliente de notificacion de transmision automatica de mensajes para dispositivos de usuarios multiples.
US9195479B2 (en) Selective notification of native applications
JP2016507795A (ja) 予測位置の通知
US9519506B2 (en) Method and apparatus for enabling remote service task based access to functionality provided by one or more remote services
CN110785970A (zh) 使网页的机器人创建自动化的技术
US8200766B2 (en) Social networking runtime
WO2013082898A1 (zh) 一种业务数据的呈现方法、终端、服务器及***
US10664242B2 (en) Application development engine and method of performing same
US20180219892A1 (en) Methods and Systems for Detecting Viruses in Emails
WO2014063547A1 (zh) 自动提示用户注册微博的方法、装置及***
CN110708238A (zh) 用于处理信息的方法和装置
US20220084078A1 (en) Methods and Systems for Untargeting Users of an Online Service for Advertising
Fisher Lessons learned from the post-George Floyd protests
TWI495369B (zh) 行動通訊裝置訊息提供方法
Wolf Education and Health Standing Committee-Guide for submissions-Inquiry into support for autistic children and young people in

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 14853807

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 14853807

Country of ref document: EP

Kind code of ref document: A1