CN104573069A - Enterprise portal front-end rendering engine - Google Patents
Enterprise portal front-end rendering engine Download PDFInfo
- Publication number
- CN104573069A CN104573069A CN201510037490.7A CN201510037490A CN104573069A CN 104573069 A CN104573069 A CN 104573069A CN 201510037490 A CN201510037490 A CN 201510037490A CN 104573069 A CN104573069 A CN 104573069A
- Authority
- CN
- China
- Prior art keywords
- data
- interface
- shell
- menu
- layout
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/242—Query formulation
- G06F16/2428—Query predicate definition using graphical user interfaces, including menus and forms
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/957—Browsing optimisation, e.g. caching or content distillation
- G06F16/9574—Browsing optimisation, e.g. caching or content distillation of access to content, e.g. by caching
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Human Computer Interaction (AREA)
- Mathematical Physics (AREA)
- Computational Linguistics (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The invention discloses an enterprise portal front-end rendering engine. After a portal is designed with a designer, a package, skin, a menu and an interface in a designer database are assembled in a browser with javascript technique, static file formatting is performed, then data are extracted from a static file to perform picture rendering, the browser is stored in a cache after being downloaded for one time during use, fixed data are assembled to a complete portal interface through algorithm, the problem about bottleneck of server performance is solved, data in a static file storage database are adopted, the principle of caching the static file with the client browser is utilized, some unchanged files only need to be loaded once without reloading, when the data are read, the interface data are only read from the static file, and accordingly interface response time is shortened while server pressure is lowered.
Description
Technical field
The present invention relates to areas of information technology, specifically, is enterprise portal front end render engine.
Background technology
For a long time, enterprise portal is all adopt traditional mode to represent door, is namely calculated at server end by JSP/ASP, then sends a large amount of words to client.Such drawback is exactly that server needs a large amount of computings and takies many bandwidth.If customer volume is many, certain pressure can be caused to server.
Enterprise portal adopts server operation, and the interface finally generated is sent to client.If time customer volume reaches a lot, need constantly to promote hardware performance to support a large amount of computings, high performance hardware device cost is higher and cannot the problem at thorough settlement server generation interface.
Summary of the invention
The object of the present invention is to provide enterprise portal front end render engine, settlement server performance bottleneck problem, adopt the data in staticize file storage database, utilize the principle of client browser caching static file, some does not have vicissitudinous file only to need loading once just need not again load, and when reading data, interface data only needs to read from static file, thus shorten the interface response time, reduce server stress.
The present invention is achieved through the following technical solutions: after designing door with designer, by the shell in designer database, skin, menu, interface with javascript Technical form in browser, carry out static file format, then from static file, take out data carry out picture and play up, in use browser downloads once after, deposit in the buffer, and fixing data assembling become a complete portal interface by algorithm, settlement server performance bottleneck problem, adopt the data in staticize file storage database, utilize the principle of client browser caching static file, some does not have vicissitudinous file only to need loading once just need not again load, when reading data, interface data only needs to read from static file, thus shorten the interface response time, reduce server stress.
Further, to better implement the present invention, described designer designs door and comprises following concrete steps:
(1) by door model data, shell model data, menu model data, skin model data, INTERFACE MODEL data integration in designer database;
(2) shell is played up: from shell model data, take out data, data assembling is become tree, gives shell rendering layer by the data after assembling; Shell content taking-up javascript technology is rendered in browser by shell rendering layer;
(3) skin is played up: CSS routing information data are formed legal link label data, give skin rendering layer by link label data by the CSS routing information data of taking out use from skin model data; Link label javascript technology is rendered in browser by skin rendering layer;
(4) menu is played up: from menu model data, take out menu object, takes out the interface data that user sets up, menu object and interface data are passed to menu rendering layer from INTERFACE MODEL data; Template in menu object and interface data are assembled into a complete HTML fragment javascript technology and are rendered into the menu area of specifying in shell by menu rendering layer;
(5) interface is contaminated: layout table data and component table data are taken out in INTERFACE MODEL data, layout table data and component table data are passed to interface rendering layer; Interface rendering layer obtains the current interface chosen, and is taken out by the assembly needed in layout and interface; Layout content is rendered into the content regions that shell is specified, and assembly is rendered in layout by the position javascript technology finding assembly will be rendered in layout in each assembly;
(6) door design is completed.
Further, to better implement the present invention, described shell impregnation layer is that physical layer interface receives only data to play up door shell, specifies menu, content regions display position in shell; Described skin impregnation layer is that physical layer interface receives only data to play up portal skin.
Further, to better implement the present invention, described " by the shell in designer database, skin, menu, interface javascript Technical form in browser; carry out static file format; then take out data and carry out picture and play up from static file; in use browser downloads once after, deposit in the buffer, and fixing data assembling become a complete portal interface by algorithm " comprise following concrete steps:
1) front end formatted data process: become by the data transformations in designer database the word of JSON form to be stored in the static file of browser support, static file exists with JS document form;
2) shell is played up: from static file, obtain shell model data, and shell model data is passed to shell rendering layer; Shell content taking-up javascript technology is rendered in browser by shell rendering layer;
3) menu is played up: the interface data taking out menu object and user's foundation from static file, and menu object and interface data are passed to menu rendering layer; Template in menu object and interface data are assembled into a complete HTML fragment javascript technology and are rendered into the menu area of specifying in shell by menu rendering layer;
4) interface is contaminated: from static file, take out layout table data and component table data, layout table data and component table data are passed to interface rendering layer; Interface rendering layer obtains the current interface chosen, and is taken out by the assembly needed in layout and interface; Layout content is rendered into the content regions that shell is specified, and assembly is rendered in layout by the position javascript technology finding assembly will be rendered in layout in each assembly;
5) complete portal interface is formed.
Further, to better implement the present invention, described shell impregnation layer is that physical layer interface receives only data to play up door shell, specifies menu, content regions display position in shell; Described skin impregnation layer is that physical layer interface receives only data to play up portal skin.
Further, to better implement the present invention, layout and assembly is provided with in described interface.
The present invention compared with prior art, has the following advantages and beneficial effect:
(1) settlement server performance bottleneck problem of the present invention, adopt the data in staticize file storage database, utilize the principle of client browser caching static file, some does not have vicissitudinous file only to need loading once just need not again load, when reading data, interface data only needs to read from static file, thus shortens the interface response time, reduces server stress.
(2) not only the present invention in use, computings a large amount of for interface can be disperseed, to each client, to alleviate server stress but also save bandwidth.
(3) the present invention fetches data and carries out picture and play up and adopt interface mode from database, and from static file, taking out data, to carry out that picture plays up be after door is issued, and provides access interface for a large amount of users.
(4) the present invention utilizes browser can the file of buffer memory website, reduces request, and the waste of bandwidth; Utilize the feature of JSON, when storage object information, store with tree structure, be convenient to search and use.
(5) the present invention in use, after HTML loads javascript file, is exactly objectification, do not need doing any process when browser end uses.
Accompanying drawing explanation
Fig. 1 is process flow diagram of the present invention.
Embodiment
Below in conjunction with embodiment, the present invention is described in further detail, but embodiments of the present invention are not limited thereto.
Enterprise portal: one connects enterprises and outside website, it can provide the entrance of single various information resources of access enterprise for enterprise, and the employee of enterprise, client, affiliate and supplier etc. can obtain personalized information and service by this door.
Front end: client (Client) or be called user side, refers to corresponding with server, for client provides the program of local service.Except some are only except the application program of local runtime, be generally arranged in common client computer, needing works in coordination with service end runs.
Play up: from the process of model generation image.Model is that it comprises geometry, viewpoint, texture and illumination information with the description for three-dimensional body of the language of strict difinition or data structure.
Embodiment 1:
Enterprise portal front end render engine, after designing door with designer, by the shell in designer database, skin, menu, interface with javascript Technical form in browser, carry out static file format, then from static file, take out data carry out picture and play up, in use browser downloads once after, deposit in the buffer, and fixing data assembling become a complete portal interface by algorithm, settlement server performance bottleneck problem, adopt the data in staticize file storage database, utilize the principle of client browser caching static file, some does not have vicissitudinous file only to need loading once just need not again load, when reading data, interface data only needs to read from static file, thus shorten the interface response time, reduce server stress.
Embodiment 2:
The present embodiment is at the enterprising one-step optimization in the basis of above-described embodiment, and further, to better implement the present invention, described designer designs door and comprises following concrete steps:
(1) by door model data, shell model data, menu model data, skin model data, INTERFACE MODEL data integration in designer database;
(2) shell is played up: from shell model data, take out data, data assembling is become tree, gives shell rendering layer by the data after assembling; Shell content taking-up javascript technology is rendered in browser by shell rendering layer;
(3) skin is played up: CSS routing information data are formed legal link label data, give skin rendering layer by link label data by the CSS routing information data of taking out use from skin model data; Link label javascript technology is rendered in browser by skin rendering layer;
(4) menu is played up: from menu model data, take out menu object, takes out the interface data that user sets up, menu object and interface data are passed to menu rendering layer from INTERFACE MODEL data; Template in menu object and interface data are assembled into a complete HTML fragment javascript technology and are rendered into the menu area of specifying in shell by menu rendering layer;
(5) interface is contaminated: layout table data and component table data are taken out in INTERFACE MODEL data, layout table data and component table data are passed to interface rendering layer; Interface rendering layer obtains the current interface chosen, and is taken out by the assembly needed in layout and interface; Layout content is rendered into the content regions that shell is specified, and assembly is rendered in layout by the position javascript technology finding assembly will be rendered in layout in each assembly;
(6) door design is completed.
Embodiment 3:
The present embodiment is at the enterprising one-step optimization in the basis of above-described embodiment, and further, to better implement the present invention, described shell impregnation layer is that physical layer interface receives only data to play up door shell, specifies menu, content regions display position in shell; Described skin impregnation layer is that physical layer interface receives only data to play up portal skin.
Embodiment 4:
The present embodiment is at the enterprising one-step optimization in the basis of above-mentioned any embodiment, further, to better implement the present invention, described " by the shell in designer database, skin, menu, interface javascript Technical form in browser; carry out static file format; then take out data and carry out picture and play up from static file; in use browser downloads once after; deposit in the buffer, and fixing data assembling become a complete portal interface by algorithm " comprise following concrete steps:
1) front end formatted data process: become by the data transformations in designer database the word of JSON form to be stored in the static file of browser support, static file exists with JS document form;
2) shell is played up: from static file, obtain shell model data, and shell model data is passed to shell rendering layer; Shell content taking-up javascript technology is rendered in browser by shell rendering layer;
3) menu is played up: the interface data taking out menu object and user's foundation from static file, and menu object and interface data are passed to menu rendering layer; Template in menu object and interface data are assembled into a complete HTML fragment javascript technology and are rendered into the menu area of specifying in shell by menu rendering layer;
4) interface is contaminated: from static file, take out layout table data and component table data, layout table data and component table data are passed to interface rendering layer; Interface rendering layer obtains the current interface chosen, and is taken out by the assembly needed in layout and interface; Layout content is rendered into the content regions that shell is specified, and assembly is rendered in layout by the position javascript technology finding assembly will be rendered in layout in each assembly;
5) complete portal interface is formed.
Embodiment 5:
The present embodiment is at the enterprising one-step optimization in the basis of above-described embodiment, and further, to better implement the present invention, described shell impregnation layer is that physical layer interface receives only data to play up door shell, specifies menu, content regions display position in shell; Described skin impregnation layer is that physical layer interface receives only data to play up portal skin.
Embodiment 6:
The present embodiment is at the enterprising one-step optimization in the basis of embodiment 1, further, to better implement the present invention, is provided with layout and assembly in described interface.
Embodiment 7:
The present embodiment is at the enterprising one-step optimization in the basis of above-mentioned any embodiment, and as shown in Figure 1, user utilizes designer to carry out door design, specifically adopts following steps:
(1) " designer database data " process: by door model data, shell model data, menu model data, skin model data, INTERFACE MODEL data integration in designer database, the packet of each model is containing conventional essential information, as, title, details, size, content, style path etc.;
(2) shell DB data processing carry out shell and play up: take out data from shell model data, data assembling is become tree, give shell rendering layer by the data after assembling; Shell content taking-up javascript technology is rendered in browser by shell rendering layer;
(3) skin Dynamic Data Processing carry out skin and play up: CSS routing information data are formed legal link label data, give skin rendering layer by link label data by the CSS routing information data of taking out use from skin model data; Link label javascript technology is rendered in browser by skin rendering layer;
(4) menu dynamic data processing carry out menu and play up: take out menu object from menu model data, take out the interface data that user sets up from INTERFACE MODEL data, menu object and interface data are passed to menu rendering layer; Template in menu object and interface data are assembled into a complete HTML fragment javascript technology and are rendered into the menu area of specifying in shell by menu rendering layer;
(5) layout component Dynamic Data Processing carry out interface dip-dye: in INTERFACE MODEL data, layout table data and component table data are taken out, layout table data and component table data are passed to interface rendering layer; Interface rendering layer obtains the current interface chosen, and is taken out by the assembly needed in layout and interface; Layout content is rendered into the content regions that shell is specified, and assembly is rendered in layout by the position javascript technology finding assembly will be rendered in layout in each assembly;
(6) door design is completed.
After with designer door having been designed, by the shell in designer database, skin, menu, interface with javascript Technical form in browser, carry out static file format, then from static file, take out data carry out picture and play up, in use browser downloads once after, deposit in the buffer, and fixing data assembling become a complete portal interface by algorithm, specifically comprise the following steps:
1) front end formatted data process: become by the data transformations in designer database the word of JSON form to be stored in the static file of browser support, static file exists with JS document form;
2) process of shell static data and shell are played up: from static file, obtain shell model data, and shell model data is passed to shell rendering layer; Shell content taking-up javascript technology is rendered in browser by shell rendering layer;
3) process of skin static data and skin are played up, owing to being created in html interface by the link label data information of skin when door designs, so step does not need calling data process;
4) process of menu static data and menu are played up: the interface data taking out menu object and user's foundation from static file, and menu object and interface data are passed to menu rendering layer; Template in menu object and interface data are assembled into a complete HTML fragment javascript technology and are rendered into the menu area of specifying in shell by menu rendering layer;
5) process of layout component static data and interface are contaminated: from static file, take out layout table data and component table data, layout table data and component table data are passed to interface rendering layer; Interface rendering layer obtains the current interface chosen, and is taken out by the assembly needed in layout and interface; Layout content is rendered into the content regions that shell is specified, and assembly is rendered in layout by the position javascript technology finding assembly will be rendered in layout in each assembly;
6) form complete portal interface, be convenient to user access.
Settlement server performance bottleneck problem of the present invention, adopt the data in staticize file storage database, utilize the principle of client browser caching static file, some does not have vicissitudinous file only to need loading once just need not again load, when reading data, interface data only needs to read from static file, thus shortens the interface response time, reduces server stress.
The above is only preferred embodiment of the present invention, and not do any pro forma restriction to the present invention, every any simple modification, equivalent variations done above embodiment according to technical spirit of the present invention, all falls within protection scope of the present invention.
Claims (6)
1. enterprise portal front end render engine, it is characterized in that: after designing door with designer, by the shell in designer database, skin, menu, interface with javascript Technical form in browser, carry out static file format, then from static file, take out data carry out picture and play up, in use browser downloads once after, deposit in the buffer, and fixing data assembling become a complete portal interface by algorithm.
2. enterprise portal front end according to claim 1 render engine, is characterized in that: described designer designs door and comprises following concrete steps:
(1) by door model data, shell model data, menu model data, skin model data, INTERFACE MODEL data integration in designer database;
(2) shell is played up: from shell model data, take out data, data assembling is become tree, gives shell rendering layer by the data after assembling; Shell content taking-up javascript technology is rendered in browser by shell rendering layer;
(3) skin is played up: CSS routing information data are formed legal link label data, give skin rendering layer by link label data by the CSS routing information data of taking out use from skin model data; Link label javascript technology is rendered in browser by skin rendering layer;
(4) menu is played up: from menu model data, take out menu object, takes out the interface data that user sets up, menu object and interface data are passed to menu rendering layer from INTERFACE MODEL data; Template in menu object and interface data are assembled into a complete HTML fragment javascript technology and are rendered into the menu area of specifying in shell by menu rendering layer;
(5) interface is contaminated: layout table data and component table data are taken out in INTERFACE MODEL data, layout table data and component table data are passed to interface rendering layer; Interface rendering layer obtains the current interface chosen, and is taken out by the assembly needed in layout and interface; Layout content is rendered into the content regions that shell is specified, and assembly is rendered in layout by the position javascript technology finding assembly will be rendered in layout in each assembly;
(6) door design is completed.
3. enterprise portal front end according to claim 2 render engine, is characterized in that: described shell impregnation layer is that physical layer interface receives only data to play up door shell, specifies menu, content regions display position in shell; Described skin impregnation layer is that physical layer interface receives only data to play up portal skin.
4. the enterprise portal front end render engine according to claim 1 or 2 or 3, it is characterized in that: described " by the shell in designer database, skin, menu, interface javascript Technical form in browser; carry out static file format; then take out data and carry out picture and play up from static file; in use browser downloads once after; deposit in the buffer, and fixing data assembling become a complete portal interface by algorithm " comprise following concrete steps:
1) front end formatted data process: become by the data transformations in designer database the word of JSON form to be stored in the static file of browser support, static file exists with JS document form;
2) shell is played up: from static file, obtain shell model data, and shell model data is passed to shell rendering layer; Shell content taking-up javascript technology is rendered in browser by shell rendering layer;
3) menu is played up: the interface data taking out menu object and user's foundation from static file, and menu object and interface data are passed to menu rendering layer; Template in menu object and interface data are assembled into a complete HTML fragment javascript technology and are rendered into the menu area of specifying in shell by menu rendering layer;
4) interface is contaminated: from static file, take out layout table data and component table data, layout table data and component table data are passed to interface rendering layer; Interface rendering layer obtains the current interface chosen, and is taken out by the assembly needed in layout and interface; Layout content is rendered into the content regions that shell is specified, and assembly is rendered in layout by the position javascript technology finding assembly will be rendered in layout in each assembly;
5) complete portal interface is formed.
5. enterprise portal front end according to claim 4 render engine, is characterized in that: described shell impregnation layer is that physical layer interface receives only data to play up door shell, specifies menu, content regions display position in shell; Described skin impregnation layer is that physical layer interface receives only data to play up portal skin.
6. enterprise portal front end according to claim 1 render engine, is characterized in that: be provided with layout and assembly in described interface.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510037490.7A CN104573069A (en) | 2015-01-26 | 2015-01-26 | Enterprise portal front-end rendering engine |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510037490.7A CN104573069A (en) | 2015-01-26 | 2015-01-26 | Enterprise portal front-end rendering engine |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN104573069A true CN104573069A (en) | 2015-04-29 |
Family
ID=53089131
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510037490.7A Pending CN104573069A (en) | 2015-01-26 | 2015-01-26 | Enterprise portal front-end rendering engine |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN104573069A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105302562A (en) * | 2015-11-09 | 2016-02-03 | 深圳市宏辉智通科技有限公司 | Software development system and mode based on template design under Android platform |
| CN106528104A (en) * | 2016-10-31 | 2017-03-22 | 用友网络科技股份有限公司 | Method for portal layout rendering |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1783079A (en) * | 2004-11-30 | 2006-06-07 | 阿尔卡特公司 | Method of displaying data of a client computer |
| US20070204013A1 (en) * | 2006-01-12 | 2007-08-30 | Castrucci David P | Method and apparatus for creating a website |
| CN103034731A (en) * | 2012-12-20 | 2013-04-10 | 北京思特奇信息技术股份有限公司 | Method for generating Web front-end interactive page |
| CN103853716A (en) * | 2012-11-28 | 2014-06-11 | 纽海信息技术（上海）有限公司 | Webpage display system and method |
-
2015
- 2015-01-26 CN CN201510037490.7A patent/CN104573069A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1783079A (en) * | 2004-11-30 | 2006-06-07 | 阿尔卡特公司 | Method of displaying data of a client computer |
| US20070204013A1 (en) * | 2006-01-12 | 2007-08-30 | Castrucci David P | Method and apparatus for creating a website |
| CN103853716A (en) * | 2012-11-28 | 2014-06-11 | 纽海信息技术（上海）有限公司 | Webpage display system and method |
| CN103034731A (en) * | 2012-12-20 | 2013-04-10 | 北京思特奇信息技术股份有限公司 | Method for generating Web front-end interactive page |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105302562A (en) * | 2015-11-09 | 2016-02-03 | 深圳市宏辉智通科技有限公司 | Software development system and mode based on template design under Android platform |
| CN106528104A (en) * | 2016-10-31 | 2017-03-22 | 用友网络科技股份有限公司 | Method for portal layout rendering |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103502983B (en) | Memoizing Web-browsing computation with DOM-based isomorphism | |
| KR101824222B1 (en) | Fast rendering of websites containing dynamic content and stale content | |
| US20150286739A1 (en) | Html5-protocol-based webpage presentation method and device | |
| CN107766532A (en) | A kind of front end Node.js automates positive static method | |
| US20180276308A1 (en) | Method and system for increasing page loading rate | |
| US20080244740A1 (en) | Browser-independent editing of content | |
| US20120110437A1 (en) | Style and layout caching of web content | |
| CN103699674A (en) | Webpage storing method, webpage opening method, webpage storing device, webpage opening device and webpage browsing system | |
| JP6203374B2 (en) | Web page style address integration | |
| CN110908712A (en) | Data processing method and equipment for cross-platform mobile terminal | |
| US20150185994A1 (en) | Local Rendering of an Object as an Image | |
| CN107590145A (en) | A kind for the treatment of method and apparatus of page static resource | |
| US11663288B2 (en) | Just-in-time front end template generation using logical document object models | |
| CN105094753A (en) | Method, device, and system for drawing wireframe | |
| US11720407B2 (en) | Resource pre-fetch using age threshold | |
| CN111723314B (en) | Webpage display method and device, electronic equipment and computer readable storage medium | |
| CN104573069A (en) | Enterprise portal front-end rendering engine | |
| US20190121620A1 (en) | Extensible javascript-based data visualization toolkit | |
| US10084852B1 (en) | Separated device detection architecture | |
| CN107688650A (en) | A kind of web page generation method and device | |
| US11687613B2 (en) | Generating lossless static object models of dynamic webpages | |
| CN107391175A (en) | Control data collocation method and computer-readable recording medium | |
| CN113448649B (en) | Redis-based home page data loading server and method | |
| CN109857966A (en) | A kind of optimization method and browser of browser dynamically load web page resources | |
| CN104965924B (en) | A kind of date storage method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20150429 |