CN103167014B - A kind of method and apparatus applied browser and share resource - Google Patents

A kind of method and apparatus applied browser and share resource Download PDF

Info

Publication number
CN103167014B
CN103167014B CN201210526250.XA CN201210526250A CN103167014B CN 103167014 B CN103167014 B CN 103167014B CN 201210526250 A CN201210526250 A CN 201210526250A CN 103167014 B CN103167014 B CN 103167014B
Authority
CN
China
Prior art keywords
browser
user
browser client
contacting identifiers
shared
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.)
Active
Application number
CN201210526250.XA
Other languages
Chinese (zh)
Other versions
CN103167014A (en
Inventor
陈明杰
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing aoyi Xiaosheng Technology Co.,Ltd.
Original Assignee
MAXTHON INTERNATIONAL Ltd
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 MAXTHON INTERNATIONAL Ltd filed Critical MAXTHON INTERNATIONAL Ltd
Priority to CN201210526250.XA priority Critical patent/CN103167014B/en
Publication of CN103167014A publication Critical patent/CN103167014A/en
Application granted granted Critical
Publication of CN103167014B publication Critical patent/CN103167014B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Abstract

The invention discloses a kind of method and apparatus applied browser and share resource, comprise the following steps: S1, server create and safeguard browser client list, preserve in described browser client list the corresponding relation of the first browser client ID and first user contacting identifiers, the second browser client ID and second user's contacting identifiers corresponding relation ... the corresponding relation of N browser client ID and N user's contacting identifiers; S2, described first browser create and safeguard good friend's address list, described good friend's address list for preserve second good friend's title and described second browser client ID and second user's contacting identifiers corresponding relation ... the corresponding relation of N good friend title and described N browser client ID and N user's contacting identifiers.Can make directly fast to share file between browser client, and without the need to switching back and forth between various client or application, save user time, improve the experience degree of browser client.

Description

A kind of method and apparatus applied browser and share resource
Technical field
The present invention relates to internet, applications field, particularly relate to a kind of method and apparatus applied browser and share resource.
Background technology
The development of current internet is very rapid, and netizen's quantity is rising year by year, and the Computer Mediated Communication circle of people also becomes the major way of people's contacts gradually.Joyful picture or useful file has been had also to wish to share together with friend, when but the picture that in network process, discovery one is good on use browser at present or article are want to share with good friend, general all needs logs in mailbox transmission, or go again to share after logging in instant message client or other some application, so just very inconvenient, because needs switch back and forth in browser and other application programs, cause the system resource of not only losing time but also wasting equipment for surfing the net, the people accepting equally to share does not have good experience yet.
Summary of the invention
The object of the present invention is to provide a kind of method and apparatus fast can shared from browser to browser, thus solve the foregoing problems existed in prior art.
To achieve these goals, the technical solution used in the present invention is as follows:
Apply the method that resource shared by browser, comprise the following steps:
S1, server creates and safeguards browser client list, preserves the corresponding relation of the first browser client ID and first user contacting identifiers, the second browser client ID and corresponding relation ... the N browser client ID of second user's contacting identifiers and the corresponding relation of N user's contacting identifiers in described browser client list;
S2, described first browser creates and safeguards good friend's address list, and described good friend's address list is for preserving second good friend's title and described second browser client ID and corresponding relation ... N good friend's title of second user's contacting identifiers and the corresponding relation of described N browser client ID and N user's contacting identifiers.
S3, after described first browser receives and shares instruction, judges whether preserve described second browser client ID in described good friend's address list;
If preserve described second browser client ID in described good friend's address list, then upload onto the server comprising the message needing to be shared the second browser client ID that file is shared with reception;
If not yet preserve described second browser client ID in described good friend's address list, then upload onto the server comprising the message needing to be shared second user's contacting identifiers that file is shared with reception; Described second user's contacting identifiers is the user's contacting identifiers be kept in described good friend's address list or the user contacting identifiers corresponding with second good friend's title newly inputted.
Preferably, further comprising the steps of before S3:
Described first browser is by the first browser client ID logon server;
Preferably, further comprising the steps of after S3:
If described server receives to comprise and needs to share file and the message receiving the second browser client ID shared, then file push described to be shared is given the second browser being signed in server by the second browser client ID;
If described server receives to comprise and needs to share file and the message receiving the second user's contacting identifiers shared, then in described browser client list, retrieval obtains the second browser client ID corresponding with described second user's contacting identifiers, then file push to be shared is given the second browser being signed in server by the second browser client ID;
If do not retrieve the second browser client ID corresponding with described second user's contacting identifiers in described browser client list, then send reminder message to described second user's contacting identifiers.
Preferably,
Described reminder message is used for reminding user and installs described browser and log in browser client ID, receives and shares file, logs in other network applications reception and shares file.
Preferably, described user's contacting identifiers comprises one or more in e-mail address, instant message address, phone number and microblogging address.
Preferably, described in, file to be shared comprises one or more in picture, video, audio frequency, text, network address and data file.
Apply the device that resource shared by browser, comprising:
Server, described server creates and safeguards browser client list, preserves the corresponding relation of the first browser client ID and first user contacting identifiers, the second browser client ID and corresponding relation ... the N browser client ID of second user's contacting identifiers and the corresponding relation of N user's contacting identifiers in described browser client list;
First browser, described first browser creates and safeguards good friend's address list, and described good friend's address list is for preserving second good friend's title and described second browser client ID and corresponding relation ... N good friend's title of second user's contacting identifiers and the corresponding relation of described N browser client ID and N user's contacting identifiers;
After described first browser receives and shares instruction, judge in described good friend's address list, whether to preserve described second browser client ID
If preserve described second browser client ID in described good friend's address list, then upload onto the server comprising the message needing to be shared the second browser client ID that file is shared with reception;
If not yet preserve described second browser client ID in described good friend's address list, then upload onto the server comprising the message needing to be shared second user's contacting identifiers that file is shared with reception; Described second user's contacting identifiers is the user's contacting identifiers be kept in described good friend's address list or the user contacting identifiers corresponding with second good friend's title newly inputted.
The invention has the beneficial effects as follows:
Apply after application browser of the present invention shares the method and apparatus of resource, can make directly fast to share file between browser client, and without the need to switching back and forth between various client or application, save user time, improve the experience degree of browser client.
Accompanying drawing explanation
Fig. 1 is the flow chart of steps that the method for resource shared by application browser of the present invention;
Fig. 2 is the structural representation that the device of resource shared by application browser of the present invention.
Embodiment
In order to make object of the present invention, technical scheme and advantage clearly understand, below in conjunction with accompanying drawing, the present invention is further elaborated.Should be appreciated that embodiment described herein only in order to explain the present invention, be not intended to limit the present invention.
As shown in Figure 1, the invention discloses the method fast can shared from browser to browser to comprise the following steps:
S1, server creates and safeguards browser client list, preserves the corresponding relation of the first browser client ID and first user contacting identifiers, the second browser client ID and corresponding relation ... the N browser client ID of second user's contacting identifiers and the corresponding relation of N user's contacting identifiers in described browser client list;
S2, described first browser creates and safeguards good friend's address list, and described good friend's address list is for preserving second good friend's title and described second browser client ID and corresponding relation ... N good friend's title of second user's contacting identifiers and the corresponding relation of described N browser client ID and N user's contacting identifiers.
Described first browser is by the first browser client ID logon server;
S3, after described first browser receives and shares instruction, judges whether preserve described second browser client ID in described good friend's address list;
If preserve described second browser client ID in described good friend's address list, then upload onto the server comprising the message needing to be shared the second browser client ID that file is shared with reception;
If not yet preserve described second browser client ID in described good friend's address list, then upload onto the server comprising the message needing to be shared second user's contacting identifiers that file is shared with reception; Described second user's contacting identifiers is the user's contacting identifiers be kept in described good friend's address list or the user contacting identifiers corresponding with second good friend's title newly inputted.
If described server receives to comprise and needs to share file and the message receiving the second browser client ID shared, then file push described to be shared is given the second browser being signed in server by the second browser client ID;
If described server receives to comprise and needs to share file and the message receiving the second user's contacting identifiers shared, then in described browser client list, retrieval obtains the second browser client ID corresponding with described second user's contacting identifiers, then file push to be shared is given the second browser being signed in server by the second browser client ID;
If do not retrieve the second browser client ID corresponding with described second user's contacting identifiers in described browser client list, then send reminder message to described second user's contacting identifiers.
Described reminder message is used for reminding user and installs described browser and log in browser client ID, receives and shares file, logs in other network applications (such as mailbox etc.) reception and shares file.
Described user's contacting identifiers comprises one or more in e-mail address, instant message address, phone number and microblogging address.
File described to be shared comprises one or more in picture, video, audio frequency, text, network address and data file.
Can be the origin network address (finding the address of these Internet resources when browsing) of a resource file when sharing, also can be uploaded by the first browser and preserve the network address in the server.
As shown in Figure 2, the invention discloses a kind of device applied browser and share resource, comprising:
Server, described server creates and safeguards browser client list, preserves the corresponding relation of the first browser client ID and first user contacting identifiers, the second browser client ID and corresponding relation ... the N browser client ID of second user's contacting identifiers and the corresponding relation of N user's contacting identifiers in described browser client list;
First browser, described first browser creates and safeguards good friend's address list, and described good friend's address list is for preserving second good friend's title and described second browser client ID and corresponding relation ... N good friend's title of second user's contacting identifiers and the corresponding relation of described N browser client ID and N user's contacting identifiers; After described first browser receives and shares instruction, judge in described good friend's address list, whether to preserve described second browser client ID
If preserve described second browser client ID in described good friend's address list, then upload onto the server comprising the message needing to be shared the second browser client ID that file is shared with reception;
If not yet preserve described second browser client ID in described good friend's address list, then upload onto the server comprising the message needing to be shared second user's contacting identifiers that file is shared with reception; Described second user's contacting identifiers is the user's contacting identifiers be kept in described good friend's address list or the user contacting identifiers corresponding with second good friend's title newly inputted.
By adopting technique scheme disclosed by the invention, obtain effect useful as follows:
Apply after application browser of the present invention shares the method and apparatus of resource, can make directly fast to share file between browser client, and without the need to switching back and forth between various client or application, save user time, improve the experience degree of browser client.
The above is only the preferred embodiment of the present invention; it should be pointed out that for those skilled in the art, under the premise without departing from the principles of the invention; can also make some improvements and modifications, these improvements and modifications also should look protection scope of the present invention.

Claims (5)

1. apply the method that resource shared by browser, it is characterized in that, comprise the following steps:
S1, server create and safeguard browser client list, preserve in described browser client list the corresponding relation of the first browser client ID and first user contacting identifiers, the second browser client ID and second user's contacting identifiers corresponding relation ... the corresponding relation of N browser client ID and N user's contacting identifiers;
S2, described first browser create and safeguard good friend's address list, described good friend's address list for preserve second good friend's title and described second browser client ID and second user's contacting identifiers corresponding relation ... the corresponding relation of N good friend title and described N browser client ID and N user's contacting identifiers;
S3, after described first browser receives and shares instruction, judges whether preserve described second browser client ID in described good friend's address list;
If preserve described second browser client ID in described good friend's address list, then upload onto the server comprising the message needing to be shared the second browser client ID that file is shared with reception;
If not yet preserve described second browser client ID in described good friend's address list, then upload onto the server comprising the message needing to be shared second user's contacting identifiers that file is shared with reception; Described second user's contacting identifiers is the user's contacting identifiers be kept in described good friend's address list or the user contacting identifiers corresponding with second good friend's title newly inputted;
Further comprising the steps of after S3:
If described server receives to comprise and needs to share file and the message receiving the second browser client ID shared, then file push described to be shared is given the second browser being signed in server by the second browser client ID;
If described server receives to comprise and needs to share file and the message receiving the second user's contacting identifiers shared, then in described browser client list, retrieval obtains the second browser client ID corresponding with described second user's contacting identifiers, then file push to be shared is given the second browser being signed in server by the second browser client ID;
If do not retrieve the second browser client ID corresponding with described second user's contacting identifiers in described browser client list, then send reminder message to described second user's contacting identifiers;
Described user's contacting identifiers comprises one or more in e-mail address, instant message address, phone number and microblogging address.
2. the method for resource shared by application browser according to claim 1, it is characterized in that, further comprising the steps of before S3:
Described first browser is by the first browser client ID logon server.
3. the method for resource shared by application browser according to claim 1, it is characterized in that,
Described reminder message is used for reminding user and installs described browser and log in browser client ID, receives and shares file, logs in other network applications reception and shares file.
4. the method for resource shared by application browser according to claim 1, it is characterized in that, described in file to be shared comprise in picture, video, audio frequency, text, network address and data file one or more.
5. apply the device that resource shared by browser, it is characterized in that, comprising:
Server, described server creates and safeguards browser client list, preserve in described browser client list the corresponding relation of the first browser client ID and first user contacting identifiers, the second browser client ID and second user's contacting identifiers corresponding relation ... the corresponding relation of N browser client ID and N user's contacting identifiers;
First browser, described first browser create and safeguard good friend's address list, described good friend's address list for preserve second good friend's title and described second browser client ID and second user's contacting identifiers corresponding relation ... the corresponding relation of N good friend title and described N browser client ID and N user's contacting identifiers;
After described first browser receives and shares instruction, judge in described good friend's address list, whether to preserve described second browser client ID;
If preserve described second browser client ID in described good friend's address list, then upload onto the server comprising the message needing to be shared the second browser client ID that file is shared with reception;
If not yet preserve described second browser client ID in described good friend's address list, then upload onto the server comprising the message needing to be shared second user's contacting identifiers that file is shared with reception; Described second user's contacting identifiers is the user's contacting identifiers be kept in described good friend's address list or the user contacting identifiers corresponding with second good friend's title newly inputted;
If described server receives to comprise and needs to share file and the message receiving the second browser client ID shared, then file push described to be shared is given the second browser being signed in server by the second browser client ID;
If described server receives to comprise and needs to share file and the message receiving the second user's contacting identifiers shared, then in described browser client list, retrieval obtains the second browser client ID corresponding with described second user's contacting identifiers, then file push to be shared is given the second browser being signed in server by the second browser client ID;
If do not retrieve the second browser client ID corresponding with described second user's contacting identifiers in described browser client list, then send reminder message to described second user's contacting identifiers;
Described user's contacting identifiers comprises one or more in e-mail address, instant message address, phone number and microblogging address.
CN201210526250.XA 2012-12-07 2012-12-07 A kind of method and apparatus applied browser and share resource Active CN103167014B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201210526250.XA CN103167014B (en) 2012-12-07 2012-12-07 A kind of method and apparatus applied browser and share resource

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201210526250.XA CN103167014B (en) 2012-12-07 2012-12-07 A kind of method and apparatus applied browser and share resource

Publications (2)

Publication Number Publication Date
CN103167014A CN103167014A (en) 2013-06-19
CN103167014B true CN103167014B (en) 2015-09-30

Family

ID=48589751

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201210526250.XA Active CN103167014B (en) 2012-12-07 2012-12-07 A kind of method and apparatus applied browser and share resource

Country Status (1)

Country Link
CN (1) CN103167014B (en)

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103716374B (en) * 2013-12-04 2017-10-17 宇龙计算机通信科技(深圳)有限公司 Share the method and server of file
CN104601638B (en) 2014-02-24 2019-06-14 腾讯科技(深圳)有限公司 Carry out the method and system of browsing device net page information transmission
CN104601641B (en) * 2014-05-23 2018-04-06 腾讯科技(深圳)有限公司 Application link sharing method, apparatus and system
CN104486397A (en) * 2014-12-10 2015-04-01 北京奇虎科技有限公司 Method for carrying out data transmission in browser, client and mobile terminal
CN104462511B (en) * 2014-12-22 2019-07-02 北京奇虎科技有限公司 Information loading method and device in the new Shipping Options Page of browser
CN106503183A (en) * 2016-10-24 2017-03-15 北京奇虎科技有限公司 A kind of handheld terminal browser page sharing method, device and handheld terminal
CN114254365A (en) * 2021-12-26 2022-03-29 迅鳐成都科技有限公司 Block chain technology-based key value data directional sharing method, device, system and storage medium

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101465817A (en) * 2007-12-19 2009-06-24 百度在线网络技术(北京)有限公司 Method, server and system for transmitting network community message
CN102413151A (en) * 2010-09-20 2012-04-11 北京搜狗科技发展有限公司 Network resource sharing method and system

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080208963A1 (en) * 2006-10-19 2008-08-28 Aviv Eyal Online File Sharing

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101465817A (en) * 2007-12-19 2009-06-24 百度在线网络技术(北京)有限公司 Method, server and system for transmitting network community message
CN102413151A (en) * 2010-09-20 2012-04-11 北京搜狗科技发展有限公司 Network resource sharing method and system

Also Published As

Publication number Publication date
CN103167014A (en) 2013-06-19

Similar Documents

Publication Publication Date Title
CN103167014B (en) A kind of method and apparatus applied browser and share resource
US10284707B2 (en) Information transmitting method, device and system, and storage medium
RU2498520C2 (en) Method of providing peer-to-peer communication on web page
TW201532409A (en) Method and system of synchroning an unread message in instant communication
CN102571941B (en) Cloud point-to-point data transmission method and system
CN104243517A (en) Content sharing method and device used between different terminals
US20120297031A1 (en) Anonymous Signalling
US9565161B2 (en) Automatically replacing localhost as hostname in URL with fully qualified domain name or IP address
CN104486388A (en) Accessing method and device of cloud storage file
CN104836783A (en) Data transmission method, device and system
EP2605460A1 (en) Method, apparatus, and system for transferring file to user of instant message system
GB2499856A (en) Managed channel for asynchronous requests
CN109788301B (en) Live broadcast method, terminal equipment, live broadcast system and computer readable storage medium of streaming media
CN103095801B (en) A kind ofly apply the method and apparatus that browser processes resource automatically
CN102185701A (en) Method and system for realizing group information interaction
CN103561063A (en) Method and terminal for logging onto set top box
CN103716230A (en) Message sending method, device and server
WO2013082898A1 (en) Method, terminal, server and system for presenting service data
US20170171339A1 (en) Advertisement data transmission method, electrnoic device and system
CN104639973B (en) Information pushing method and device
CN103888528B (en) The realization method and system that a kind of wechat terminal communicates with voice frequency terminal message
CN106385516B (en) A kind of method, apparatus and terminal of the transfer of setting business
CN105991716A (en) System and method of information sharing
CN105516933A (en) Message processing method, message processing device, mobile terminal and server
WO2014146448A1 (en) Method and system for synchronizing browser bookmarks

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
C10 Entry into substantive examination
SE01 Entry into force of request for substantive examination
C14 Grant of patent or utility model
GR01 Patent grant
TR01 Transfer of patent right

Effective date of registration: 20190118

Address after: Room 115, Building 1, Floor 1, Jimenli District, Haidian District, Beijing

Patentee after: Maxthon Internet (Beijing) Technology Co., Ltd.

Address before: Offshore Company Centre, Town Road, British Virgin Islands

Patentee before: Maxthon International Limited

TR01 Transfer of patent right
TR01 Transfer of patent right

Effective date of registration: 20201229

Address after: 100086 b1-d11, 15-11 Zhongguancun Street, Haidian District, Beijing

Patentee after: Beijing aoyi Xiaosheng Technology Co.,Ltd.

Address before: 100191 room 115, 1st floor, building 1, jimenli community, Haidian District, Beijing

Patentee before: INTERNET MAXTHON (BEIJING) TECHNOLOGY Co.,Ltd.

TR01 Transfer of patent right