Browse Prior Art Database

Mobile Device Browser's Multi-Window Management Disclosure Number: IPCOM000210357D
Publication Date: 2011-Aug-31
Document File: 7 page(s) / 238K

Publishing Venue

The Prior Art Database


The idea is that, we can necessarily mark browser windows with survival chance and organized them in 2 areas which have different window management strategies. Both user operation and browser can change window’s belonging area in a configurable way. Also, we can inform user of windows probability of being closed automatiacally in a visual way.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 30% of the total text.

Page 01 of 7

Mobile Device Browser's Multi-Window Management

Mobile devices (smart phone or tablet PC), unlike desktop, are usually limited in memory. Therefore, the Internet browsers developed on mobile devices are usually different from their PC counterpart in browsing window management .

Usually, mobile platform's browser window management strategies fall into following categories :
1. Only one single browsing window is allowed. User can open one window a time.
2. Passive multi-window control. No limit on maximum window count and rely user to close windows. For example, UCWeb on multiple platforms allows users to open as many windows as they like.

The advantage of the method is:
o User has fully control of the window life-cycle.

The drawbacks of the method are:
o Excessive memory usage by browser will impact the performance of both the browser and other processes . Machine response will get extremely slow.
o When user has opened too many windows, it is usually hard for him to seek for a window.
3. Active multi-window control. Limit the maximum window count while user can close the windows manually. User is not given the option to create new window when the number is reached. However, if user chooses to open a new window by clicking a link in an existing window, the browser will automatically find out the window that has been idle (meaning opened, but not brought to the front) for the longest time and close it.

The advantages of the methods are:
o It keeps user from opening too many windows or using up excessive memory.

The disadvantage of the method is:
o Sometimes, being idle for long time does not mean that the window to be disposed . Imagine the scenario that a user is reading news from a site and news is displayed in a new window. Although user keeps navigating from news to news, it does not mean that he/she expect the root site that contains news entries to be automatically closed . Therefore, when a window that is expected to persist gets closed by browser, user will be confused in finding the window.
o User will probably forget window's age (idle time). In this way, window closing appears to be unpredictable to user.

For the disadvantages above, there has to be an approach to manage the windows in a more reasonable way. This invention proposes a


Page 02 of 7

method that manages browser windows in an intuitive and visual way

drawbacks are get rid of.

The idea of the invention is inspired by Java's Garbage Collection (GC) mechanism, which categorizes the objects in memory into two groups: Young Generation and Old Generation, which are compacted in separated memory areas (Eden Space and Tenured Space), are allocated for the two generations, as illustrated in the chart below:

(This page contains 00 pictures or other non-text object)

Figure 1 JVM Memory Management

Usually when the memory area of the Young Generation gets full, objects with no reference will be garbage collected. Survivors from several times of GC are regarded as the ones...