[go: up one dir, main page]

WO2002044977A1 - Application d'etablissement de calendrier javascript pour des explorateurs du web internet - Google Patents

Application d'etablissement de calendrier javascript pour des explorateurs du web internet Download PDF

Info

Publication number
WO2002044977A1
WO2002044977A1 PCT/US2000/032689 US0032689W WO0244977A1 WO 2002044977 A1 WO2002044977 A1 WO 2002044977A1 US 0032689 W US0032689 W US 0032689W WO 0244977 A1 WO0244977 A1 WO 0244977A1
Authority
WO
WIPO (PCT)
Prior art keywords
user
frames
web
webserver
client
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.)
Ceased
Application number
PCT/US2000/032689
Other languages
English (en)
Inventor
Steve Mansour
Mikol Graves
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.)
New Aurora Corp
Original Assignee
Netscape Communications Corp
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 Netscape Communications Corp filed Critical Netscape Communications Corp
Priority to PCT/US2000/032689 priority Critical patent/WO2002044977A1/fr
Priority to AU2001218102A priority patent/AU2001218102A1/en
Priority to US10/398,084 priority patent/US20050278641A1/en
Publication of WO2002044977A1 publication Critical patent/WO2002044977A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • G06Q10/109—Time management, e.g. calendars, reminders, meetings or time accounting

Definitions

  • the present invention relates to web browsers and the Internet, and more specifically to calendar client applications that can run on all computer platforms and that improve calendar-server scalability.
  • Netscape Calendar is a program that allows users to manage their time more efficiently by maintaining a calendar of a user's activities. Users can place items on the calendar as needed in order to stay organized. Netscape Calendar is intended for collaborative use, so each user can access the calendars of other users and plan meetings or other events without phone calls or e-mail messages. Netscape Calendar is a part of Netscape Communicator Professional Edition and needs to activated by an administrator before it can be used. But such conventional system requires far too much support and attention from the web server.
  • Netscape Calendar includes Agenda, a sharable calendar, tasks, daily notes, and daily events.
  • Netscape Agenda also provides access to the user's tasks, daily notes, day events and reminders. Any event scheduled in a user's agenda's day, week or month view is an agenda entry. Users can create and view a user's agenda entries and, in some cases, those of others, depending on a user's access rights and the access level the creator has assigned the entry. Users may also edit any entries created in a user's name. Users can create tasks in a user's agenda. Tasks are things users have to do, but that cannot be scheduled into a user's agenda like a meeting or an appointment.
  • Such tasks appear in a task view of a user's daily agenda pages and in a user's task display.
  • Users can create daily notes in a user's agenda. Notes are entered into a user's agenda, not already entered under tasks, day events, or agenda entries.
  • the daily notes appear in the notes view of a user's daily and weekly agenda pages. A day event lasts for an entire day, without taking up time in a user's day view. Day events will appear in the notes view at the bottom of a user's agenda pages.
  • Netscape Calendar can remind users of the entries users have in it. Such reminders can be set up in a number of different ways, to suit the demands of a user's entries and a user's schedule. Users can print out a user's agenda pages. The different types of pages can be tailored to include only the information users want on a user's printouts. The fonts and margins can also b e adjusted to suit a user's needs.
  • Each Netscape Calendar server manages a database of individual calendars, the number of which is limited by the capabilities of the server hardware. As with POP/I MAP e-mail mailboxes, individual calendars always sit on the same servers, so each calendar has a "home" server.
  • Calendars also may also exist on a user's local system, and can select any number of calendars to be synchronized onto the local system.
  • the local calendars can be synchronized with a server-based calendar database. Users typically synchronize only their own calendar, but Netscape Calendar servers support making local, synchronized copies of any calendar a system. A user who is traveling could therefore bring along a whole department's calendars.
  • free/busy searches can be run on that server.
  • a user's home server must connect separately to each server to gather the free/busy information and to present a unified view.
  • the Appointnet system When an end user sends an invitation or announcement to a person who is not an Appointnet user, then the Appointnet system automatically creates a unique calendar for the recipient, and sends an e-mail to that person. Individuals who use the present system can post reminders to themselves, send announcements to people they know, and make appointments with people they know. When these messages are sent, the communication is nearly instantaneous because the system makes one record and allows both (or many) parties to view it. Such Patent is incorporated herein by reference.
  • the present invention is a calendaring system implemented as a JavaScript application for program execution on individual Internet browsers after being downloaded by a webserver.
  • the JavaScript application generates HTML on- the-fly from within invisible frames and renders such HTML on a user's screen in visible frames.
  • the result is an interactive scheduling, appointment, and calendaring system that can be shared between many users on the Internet.
  • Fig. 1 is a functional block diagram of an Internet calendaring system embodiment of the present invention.
  • Fig. 2 is a dataflow diagram of a calendaring system embodiment of the present invention in which a web-server sends frame sets that open in users' browsers as visible and invisible frames.
  • Fig. 1 is a functional block diagram of a calendar system embodiment of the present invention referred to herein by the general reference numeral 100.
  • the Internet 102 is used to interconnect network servers and clients.
  • a calendar webserver 104 provides a shared calendar control and synchronization function for many clients distributed about the Internet. Such clients and users can share and exchange calendar information to help coordinate community events, private meetings, classroom attendance, legal deadline observance, etc.
  • An output 106 transmits hypertext transfer protocol (HTTP) datapackets that include calendar core routines written in JavaScript, for example, reference user's interfaces (ref-UI) written in hypertext markup language (HTML), and calendar event data. Such are issued in response to requests and event data received in HTTP datapackets on an input 108.
  • HTTP hypertext transfer protocol
  • a number of typical web- clients and their browsers are represented by web-clients 110, 112, and 114.
  • the users as such may be independent or loosely associated in a variety of groups and special interests.
  • a remote webserver 116 can include a sponsor who pays a fee to the operator of the calendar webserver 104 to include commercial advertisements in the JS-core, ref-UI, and calendar event data on output 106.
  • the JS-core, ref-UI, and calendar event data on output 106 are received on an input 1 18 to web-client 1 10 in response to requests issued to the calendar webserver 104 over an output 120.
  • the web-client 110 may generate original calendar event data that will be stored in the calendar server and can be distributed to the appropriate users by the calendar webserver 104.
  • requested JS-core, ref-UI, and calendar event data on output 106 are received on an input 122 to web-client 112 in response to requests issued to the calendar webserver 104 over an output 124.
  • This web-client 1 12 may also generate unique and original calendar event data that needs to be distributed to the appropriate users by the calendar webserver 104.
  • the web-client 1 14 is no different.
  • An input 126 receives JS-core, ref-UI, and calendar event data on output 106.
  • An output 128 handles requests to calendar webserver 104 and any special event data generated.
  • An output 130 from the remote webserver provides advertisements and content in typical HTML and JavaScript http- datapackets. Any requests, e.g., hyperlinks clicked on by users at the web- clients 110, 112, and 114, are received on an input 132.
  • the web-clients' browsers 110, 112, and 114 must support frames, e.g., multiple windows that can be generated and controlled by the webserver 104. For example, Netscape Navigator 3.0, or later version, will be preferred.
  • the JS-core, ref-UI, and calendar event data on output 106 will initially cause a frame set to be created. Some of the frames in the frame set will be visible to the web-client users, and some will not be visible. Those that are not visible are used to interface the event data on the webserver with the visible frames on the web-client browser.
  • the ref-UI is coded in Javascript within HTML and will build a graphical user interface in a model-calendar format, e.g., days, weeks, months.
  • the JS-core is coded in JavaScript and provides interactive users control locally, e.g., from within one of the non-visible frames.
  • An initial download of event data from the webserver to the web-client will be preferably adequate to service most if not all read-only calendar interactions by a user. Any missing or needed event data will be requested as needed.
  • New, original event data generated by a user that is important for other users to have is uploaded to the webserver 104. Changes to existing event data are uploaded as well.
  • a web-client user interface is included in the calendar server.
  • a web-client user interface is generated "on-the-fly" within a user's browser.
  • a frame set is created. Several frames are visible to the user, and several frames are "hidden" and not visible on the screen.
  • One such frame includes calendar event data that was requested from the server.
  • Other frames include JavaScript routines that know how to read the event data and produce HTML to render the events or other interface elements.
  • the JavaScript running in the hidden frames emit HTML to the visible frames to render the interface seen by the users.
  • calls are made into the JavaScript routines to change the interface. For example, if the user presses the month button, the JavaScript routines will emit a monthly calendar view of data and send it to the visible frames.
  • One advantage to this approach is that a lot of processing is done in a user's browser, and a round trip to the server is not required for every button click. For example, suppose that several months worth of event data is downloaded one call to the server. Suppose that the user is viewing one day's worth of data. Now the user clicks the "next day" button. It is likely that the event data for the next day is already in the invisible data frame. Assuming it is, the JavaScript routines detect this, and emit the HTML for the next day and display it. There was no need to make a round trip request to the server. The number of requests that the server must process is reduced because many requests can be processed on the web browser by the JavaScript. Furthermore, for users with phone modem connections to the ISP, the new page can be generated much faster than a web page can be transmitted from the server.
  • Such interface generation allows links to images, ads, or other content to be accessed from a remote server.
  • the web-client code is a combination of JavaScript and HTML. It is divided into two major parts, a JS-core and a reference user-interface (Ul).
  • the JS-core includes routines to: (a) fetch, edit, create and delete calendar events, (b) login/logout, (c) import/export calendar information, (d) preference management routines, e.g., agenda list management, initial view, first day of week, time-zone, (e) calendar management routines (WCAP commands), (f) localize strings, (g) change locales, (h) set colors and fonts, (i) set themes (specific combinations of colors, fonts, and logo images), (j) format dates and time zones, and (k) date navigation, date utilities, and interface utilities.
  • preference management routines e.g., agenda list management, initial view, first day of week, time-zone
  • WCAP commands calendar management routines
  • WCAP commands calendar management routines
  • localize strings e.g., change locales, (h) set colors and fonts, (i) set themes (specific combinations of colors, fonts, and logo images), (j) format dates and time zones, and (k) date navigation, date utilities, and
  • the reference user-interface implements a calendar user interface based on the JS-core routines.
  • Such includes linked events, agendas (layers of calendars), and, public and private calendars. Users can own multiple calendars, and calendars can be owned by multiple users. Links can be embedded in web pages or e-mail messages to point to individual events or calendar views. E- mail alarms, e-mail paging, and e-mail invitations to events are also supported by the calendar web server 104.
  • User preferences typically include preferred first-day-of-week, preferred time zone, multiple time zone support, import/export/synchronization, print preview, deletion tombstones, color scheme, font scheme, sound scheme, and context-sensitive help.
  • Fig. 2 illustrates a calendaring system embodiment of the present invention, and is referred to herein by the general reference numeral 200.
  • the system 200 is based on a web-server 202 that services at least one web-client 204 over an Internet connection 206.
  • a calendar event database 208 stores coordinated, corrected, and up-to-date calendar information in condensed form.
  • a data request 210 initiated by a browser user at a network client site includes a description of what particular calendar information a user wants. This is forwarded over the Internet 206 and becomes a data request 212.
  • the appropriate data is fetched and its presentation may require certain user interfaces to deal with it.
  • the calendar event database 208 responds to queries with an event data 214 and an event-interface description 216.
  • a JavaScript generator 218 builds corresponding JavaScript routines 220 that will be executed as-needed by the web-client 204.
  • a frame set generator 222 builds a mixed event data, HTML, and JavaScript code 224 for transmission to the web-client 204.
  • such mixed event data, HTML, and JavaScript code is separated into a visible-frames data 226 and an invisible-frames data 228.
  • a frames-capable browser responds with a set of visible frames 230 that appear before the user and a set of invisible frames 232.
  • the visible frames 230 can include day, week, month, and year interactive graphical user interfaces for appointment, event, and schedule data of concern to the user.
  • the purpose of the invisible frames 232 is to host the downloaded JavaScript routines and calendar data 220.
  • a user-interface control 234 will trigger various ones of the JavaScript routines to execute and generate new user-interface HTML 236 that will render within or build more visible frames 230.
  • a "standalone” or “native” client is needed that has off-line capabilities, sync capabilities, and is feature rich.
  • these clients also had to be developed on multiple platforms (Windows, Mac, and Unix).
  • Such calendar client preferably has entirely downloadable chrome, i.e., the entire user interface look-and-feel can be downloaded to a client that understands a description language such as XML/CSS. It should look, feel, and act like a native client, and actually be an application that makes use of browser/XML/CSS technology.
  • Some embodiments of the present invention preferably can incorporate attachments to events.
  • a back-end that supports an iCalendar GEO property (geographic event location), is exposed in the interface.
  • Meeting locations are tied to mapping services to allow users to obtain personalized maps and directions to event locations.
  • Layout management tools are preferably included for customizing the interface.
  • Automated operations include adding an extra frame on the top, bottom, or side of each window, and adding links to web address on each page.
  • a fully functional calendaring system preferably incorporates portions of Netscape Messaging Server. Such enables users to exchange information within a company and across the Internet.
  • Messaging Server is controlled b y electronic mail or HTML forms and lets administrators manage users information and system-configuration parameters with the easy-to-use, point-and-click interface of Netscape Navigator and Communicator from any desktop on the network. It offers feature richness without compromising messaging interoperability or standards compliance.
  • Messaging Server version-3.5 provides numerous feature enhancements over the previous releases, including: Support for Internet Message Access Protocol Version-4 (RFC 1730) to provide messaging support for remote users, including support for IMAP4rev1 (RFC 2060) for optimal performance of message throughput.
  • RRC 1730 Support for Internet Message Access Protocol Version-4
  • IMAP4rev1 RRC 2060
  • integration with the latest release of the frames- based administration of Netscape SuiteSpot 3.1 for centralized administration of all Netscape servers; procedures for doing bulk additions, deletions, and modifications that allow quick migration of existing users.
  • Integrated NIS and NIS+ lookup capability is useful to facilitate address resolution outside of Messaging Server's domain.
  • the SSL 3.0 support in Netscape Messaging Server administration is used for secure remote administration and client communications, and LDAP version-3 support (RFC 2251 ) for centralized users management, message routing, and international character sets.
  • Authenticated SMTP to prevent unauthorized
  • EventVwr and Perfmon are included. Support is needed for messaging
  • a server application programming interface helps to develop customized transport-enable applications.
  • Messaging Server supports the Lightweight Directory Access Protocol (RFC 1777) for managing its user's information and for routing messages.
  • Messaging Server interoperates with a wide variety of third-party directory tools and Netscape Directory Server.
  • Messaging Sesver automatically creates, deletes, or changes the account when it receives an update.
  • Messaging Server uses an account database provided by any LDAP-compliant directory server.
  • IMAP4 is based on work by the University of Washington and is embodied in the RFC 1730 specification. It allows users to be disconnected from the main messaging system and still be able to process their mail. The specification allows for administrative controls for these disconnected users and for the resynchronization of the user's message store once the user reconnects to the messaging system.
  • IMAP4 as an open standard does allow for the integration of security mechanisms for the client authentication to the messaging server.
  • An encrypted messaging transport protocol is not part of the IMAP4 specification and has been developed to the S/MIME standard in Netscape Communicator.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Business, Economics & Management (AREA)
  • Theoretical Computer Science (AREA)
  • Human Resources & Organizations (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Physics & Mathematics (AREA)
  • Strategic Management (AREA)
  • General Physics & Mathematics (AREA)
  • Data Mining & Analysis (AREA)
  • General Engineering & Computer Science (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Operations Research (AREA)
  • Quality & Reliability (AREA)
  • Tourism & Hospitality (AREA)
  • General Business, Economics & Management (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

La présente invention concerne un système d'établissement de calendrier mis en oeuvre sous forme d'une application Java Script pour l'exécution du programme sur des explorateurs Internet individuels, une fois téléchargé par un serveur Web. L'application JavaScript génère un langage HTLM à la volée et une interface utilisateur graphique est affichée sur un écran. Le résultat est un système de programmation interactif qui peut être partagé entre les utilisateurs sur Internet.
PCT/US2000/032689 2000-11-30 2000-11-30 Application d'etablissement de calendrier javascript pour des explorateurs du web internet Ceased WO2002044977A1 (fr)

Priority Applications (3)

Application Number Priority Date Filing Date Title
PCT/US2000/032689 WO2002044977A1 (fr) 2000-11-30 2000-11-30 Application d'etablissement de calendrier javascript pour des explorateurs du web internet
AU2001218102A AU2001218102A1 (en) 2000-11-30 2000-11-30 Javascript calendar application for internet web browser
US10/398,084 US20050278641A1 (en) 2000-11-30 2000-11-30 Javascript Calendar Application Delivered to a Web Browser

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/US2000/032689 WO2002044977A1 (fr) 2000-11-30 2000-11-30 Application d'etablissement de calendrier javascript pour des explorateurs du web internet

Publications (1)

Publication Number Publication Date
WO2002044977A1 true WO2002044977A1 (fr) 2002-06-06

Family

ID=21742042

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2000/032689 Ceased WO2002044977A1 (fr) 2000-11-30 2000-11-30 Application d'etablissement de calendrier javascript pour des explorateurs du web internet

Country Status (2)

Country Link
AU (1) AU2001218102A1 (fr)
WO (1) WO2002044977A1 (fr)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2382188A (en) * 2001-09-28 2003-05-21 Hewlett Packard Co Collecting and distributing calendar information via a network
WO2004012104A1 (fr) * 2002-07-31 2004-02-05 Tripwire, Inc. Procede de provisionnement d'applications web reparties
WO2007007017A1 (fr) 2005-07-08 2007-01-18 Corizon Limited Procede et dispositif de modification de l'interface-utilisateur
WO2007023068A1 (fr) * 2005-08-25 2007-03-01 International Business Machines Corporation Mecanisme de generation de contenu dynamique sans serveur web
WO2012001223A1 (fr) * 2010-07-02 2012-01-05 Nokia Corporation Procédé et appareil pour démarrage dynamique de dispositif de réseau
US10489423B2 (en) 2016-12-30 2019-11-26 Microsoft Technology Licensing, Llc Most-relevant-first calendar event synchronization

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5960406A (en) * 1998-01-22 1999-09-28 Ecal, Corp. Scheduling system for use between users on the web
WO2000043898A1 (fr) * 1999-01-20 2000-07-27 Econvene, Inc. Systeme et procede destines a faciliter la reunion d'individus eloignes les uns des autres

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5960406A (en) * 1998-01-22 1999-09-28 Ecal, Corp. Scheduling system for use between users on the web
WO2000043898A1 (fr) * 1999-01-20 2000-07-27 Econvene, Inc. Systeme et procede destines a faciliter la reunion d'individus eloignes les uns des autres

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
PALMER ET AL: "Web-based tools in support of life cycle engineering of telecommunications products", ELECTRONICS MANUFACTURING TECHNOLOGY SYMPOSIUM, 1997., TWENTY-FIRST IEEE/CPMT INTERNATIONAL AUSTIN, TX, USA 13-15 OCT. 1997, NEW YORK, NY, USA,IEEE, US, 13 October 1997 (1997-10-13), pages 134 - 139, XP010249717, ISBN: 0-7803-3929-0 *
TRECORDI V ET AL: "AN EXPERIMENTAL STUDY ON THE PERFORMANCE OF WWW SERVERS", COMMUNICATIONS: THE KEY TO GLOBAL PROSPERITY. GLOBECOM 1996. GLOBAL INTERNET 96 CONFERENCE RECORD. LONDON, NOV. 18 - 22, 1996, GLOBAL TELECOMMUNICATIONS CONFERENCE (GLOBECOM), NEW YORK, IEEE, US, vol. SUPP, 18 November 1996 (1996-11-18), pages 22 - 27, XP000741667, ISBN: 0-7803-3337-3 *

Cited By (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2382188A (en) * 2001-09-28 2003-05-21 Hewlett Packard Co Collecting and distributing calendar information via a network
GB2382188B (en) * 2001-09-28 2005-03-16 Hewlett Packard Co System for collection and distribution of calendar information
US7035913B2 (en) 2001-09-28 2006-04-25 Hewlett-Packard Development Company, L.P. System for collection and distribution of calendar information
WO2004012104A1 (fr) * 2002-07-31 2004-02-05 Tripwire, Inc. Procede de provisionnement d'applications web reparties
US11194597B2 (en) * 2005-07-08 2021-12-07 Versata Fz-Llc Method and apparatus for user interface modification
US20220066797A1 (en) * 2005-07-08 2022-03-03 Versata Fz-Llc Method and Apparatus for User Interface Modification
US20100064208A1 (en) * 2005-07-08 2010-03-11 Corizon Limited Method and apparatus for user interface modification
US12182592B2 (en) * 2005-07-08 2024-12-31 Versata Fz-Llc Method and apparatus for user interface modification
US20240160455A1 (en) * 2005-07-08 2024-05-16 Versata Fz-Llc Method and Apparatus for User Interface Modification
US11915018B2 (en) * 2005-07-08 2024-02-27 Versata Fz-Llc Method and apparatus for user interface modification
US11755346B2 (en) * 2005-07-08 2023-09-12 Versata Fz-Llc Method and apparatus for user interface modification
US11126443B2 (en) * 2005-07-08 2021-09-21 Versata Fz-Llc Method and apparatus for user interface modification
WO2007007017A1 (fr) 2005-07-08 2007-01-18 Corizon Limited Procede et dispositif de modification de l'interface-utilisateur
US20210382733A1 (en) * 2005-07-08 2021-12-09 Versata Fz-Llc Method and Apparatus for User Interface Modification
WO2007023068A1 (fr) * 2005-08-25 2007-03-01 International Business Machines Corporation Mecanisme de generation de contenu dynamique sans serveur web
US7937715B2 (en) 2005-08-25 2011-05-03 International Business Machines Corporation Mechanism for generating dynamic content without a web server
US9529603B2 (en) 2010-07-02 2016-12-27 Nokia Technologies Oy Method and apparatus for dynamic network device start up
WO2012001223A1 (fr) * 2010-07-02 2012-01-05 Nokia Corporation Procédé et appareil pour démarrage dynamique de dispositif de réseau
US10489423B2 (en) 2016-12-30 2019-11-26 Microsoft Technology Licensing, Llc Most-relevant-first calendar event synchronization

Also Published As

Publication number Publication date
AU2001218102A1 (en) 2002-06-11

Similar Documents

Publication Publication Date Title
US20050278641A1 (en) Javascript Calendar Application Delivered to a Web Browser
US7003546B1 (en) Method and system for controlled distribution of contact information over a network
JP3294840B2 (ja) スケジューリング・システム
US10250672B2 (en) Method and system for controlled distribution of information over a network
US7359946B2 (en) System and method for an event planner
US20040039779A1 (en) System and method for managing information and collaborating
US20050027802A1 (en) System and method for managing information and collaborating
Zhuang et al. CyberEye: an Internet-enabled environment to support collaborative design
US20050055280A1 (en) Method, system and apparatus for internet-based sales generation
US20090112722A1 (en) Centralized consumer notification system
WO2001037123A9 (fr) Systeme d'affichage et de liaison de courrier electronique
WO2002044977A1 (fr) Application d'etablissement de calendrier javascript pour des explorateurs du web internet
Girgensohn et al. Experiences in developing collaborative applications using the World Wide Web “shell”
AU780033B2 (en) Information flow management in real time
US9088576B2 (en) Electronic media creation and distribution
JPH10214292A (ja) コンタクト手段公開装置
WO2002061608A1 (fr) Procede et dispositif pour graphiques de courrier electronique
WO2000062226A2 (fr) Systeme et procede permettant de fournir un guide ameliore d'evenements internet
WO2001043014A1 (fr) Procede et systeme servant a distribuer des messages publicitaires a des dispositifs client
WO2001043011A9 (fr) Procede de diffusion de publicites a des dispositifs clients
WO2001043374A9 (fr) Procede et systeme de distribution de publicites a des dispositifs clients

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AL AM AT AU AZ BA BB BG BR BY CA CH CN CR CU CZ DE DK DM EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG US UZ VN YU ZA

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
WWE Wipo information: entry into national phase

Ref document number: 10398084

Country of ref document: US

REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase

Ref country code: JP