Abstract: Multiple users participate in a conference while taking maximum advantage of hardware and bandwidth capabilities of each participant. Each user's system makes known to a directory service its hardware sending and receiving capabilities. The directory service makes this information available to other users who may then wish to join a conference with the user. An initiating user sends invitations via the directory service to the remote users. Each user that accepts an invitation transmits its network address to the initiating user, who then establishes a peer-to-peer connection with each of the remote users. Each participant system exchanges information about hardware capabilities and bandwidth, and a conference manager determines a best model for connecting each of the participants. Depending on the hardware and bandwidth capabilities of the participants, the manager chooses from a duplicate streams model, a multicast model, and a host-among-peers model for connecting the participants.

Abstract: Multiple users participate in a conference while taking maximum advantage of hardware and bandwidth capabilities of each participant. Each user's system makes known to a directory service its hardware sending and receiving capabilities. The directory service makes this information available to other users who may then wish to join a conference with the user. An initiating user sends invitations via the directory service to the remote users. Each user that accepts an invitation transmits its network address to the initiating user, who then establishes a peer-to-peer connection with each of the remote users. Each participant system exchanges information about hardware capabilities and bandwidth, and a conference manager determines a best model for connecting each of the participants. Depending on the hardware and bandwidth capabilities of the participants, the manager chooses from a duplicate streams model, a multicast model, and a host-among-peers model for connecting the participants.

Abstract: Multiple users participate in a conference while taking maximum advantage of hardware and bandwidth capabilities of each participant. Each user's system makes known to a directory service its hardware sending and receiving capabilities. The directory service makes this information available to other users who may then wish to join a conference with the user. An initiating user sends invitations via the directory service to the remote users. Each user that accepts an invitation transmits its network address to the initiating user, who then establishes a peer-to-peer connection with each of the remote users. Each participant system exchanges information about hardware capabilities and bandwidth, and a conference manager determines a best model for connecting each of the participants. Depending on the hardware and bandwidth capabilities of the participants, the manager chooses from a duplicate streams model, a multicast model, and a host-among-peers model for connecting the participants.

Abstract: The calendaring techniques and interfaces described herein provide access to calendar data stored in a server hosted calendar store to applications. The calendar data includes calendar events and tasks. In one aspect, an application program interface (API) retrieves an occurrence from a series of reoccurring calendar data upon request from an application. In another aspect, the API sends calendar data provided by the application to a server program that manages a calendar store for storage and queries the server program to retrieve calendar data requested by the application from the calendar store. In yet another aspect, the API sends notifications that the calendar store has changed to interested applications.

Abstract: Multiple users participate in a conference while taking maximum advantage of hardware and bandwidth capabilities of each participant. Each user's system makes known to a directory service its hardware sending and receiving capabilities. The directory service makes this information available to other users who may then wish to join a conference with the user. An initiating user sends invitations via the directory service to the remote users. Each user that accepts an invitation transmits its network address to the initiating user, who then establishes a peer-to-peer connection with each of the remote users. Each participant system exchanges information about hardware capabilities and bandwidth, and a conference manager determines a best model for connecting each of the participants. Depending on the hardware and bandwidth capabilities of the participants, the manager chooses from a duplicate streams model, a multicast model, and a host-among-peers model for connecting the participants.

Abstract: Multiple users participate in a conference while taking maximum advantage of hardware and bandwidth capabilities of each participant. Each user's system makes known to a directory service its hardware sending and receiving capabilities. The directory service makes this information available to other users who may then wish to join a conference with the user. An initiating user sends invitations via the directory service to the remote users. Each user that accepts an invitation transmits its network address to the initiating user, who then establishes a peer-to-peer connection with each of the remote users. Each participant system exchanges information about hardware capabilities and bandwidth, and a conference manager determines a best model for connecting each of the participants. Depending on the hardware and bandwidth capabilities of the participants, the manager chooses from a duplicate streams model, a multicast model, and a host-among-peers model for connecting the participants.

Abstract: A method, apparatus, and signal-bearing medium that filter data based on a criteria. In an embodiment, the criteria may be related to filtering out unwanted or junk input data. In another embodiment, the criteria may be related to filtering based on desired data. In various embodiments, the data may be email, email attachments, faxes, popup windows, telephone messages, downloaded data or programs, image data, or other data. In a embodiment, a training mode and an automatic mode are provided. During the training mode, a user may be presented with data that may be junk, and feedback may be provided that is used to train a junk filter. During an automatic mode, junk data may be removed from view, transferred to a junk box, or highlighted.

Abstract: The calendaring techniques and interfaces described herein provide access to calendar data stored in a server hosted calendar store to applications. The calendar data includes calendar events and tasks. In one aspect, an application program interface (API) retrieves an occurrence from a series of reoccurring calendar data upon request from an application. In another aspect, the API sends calendar data provided by the application to a server program that manages a calendar store for storage and queries the server program to retrieve calendar data requested by the application from the calendar store. In yet another aspect, the API sends notifications that the calendar store has changed to interested applications.