geary/src/engine/api/geary-remote-interfaces.vala

/* Copyright 2011 Yorba Foundation
 *
 * This software is licensed under the GNU Lesser General Public License
 * (version 2.1 or later).  See the COPYING file in this distribution. 
 */

public interface Geary.RemoteAccount : Object, Geary.Account {
    public abstract async string? get_folder_delimiter_async(string toplevel,
        Cancellable? cancellable = null) throws Error;
}

public interface Geary.RemoteFolder : Object, Geary.Folder {
}
Persist messages locally: #3742 This completes the heavy lifting of persisting messages locally. The strategy is that the local database may be sparsely populated, both in the availability of messages in a folder and the fields of a message that is partially stored. As data is pulled from the remote server it's always stored in the database. Future requests will always go to the database first, preventing unnecessary network traffic. Also, this patch will detect when a message is stored in multiple folders on the server. The database uses soft links from the folder to the message, so the message is stored only once in the database. This technique relies heavily on the availability and validity of the Message-ID header, but we expect this to be reliable the vast majority of the time. 2011-06-23 19:07:04 -07:00			`/* Copyright 2011 Yorba Foundation`
			`*`
			`* This software is licensed under the GNU Lesser General Public License`
			`* (version 2.1 or later). See the COPYING file in this distribution.`
			`*/`

			`public interface Geary.RemoteAccount : Object, Geary.Account {`
Folder heirarchies: #3788 Now supporting folder heirarchies. The client will now descend looking for subfolders. This task now opens up multiple outstanding requests to the Engine as well as exercises the database schema. Closing this ticket opens the door to finishing #3692. 2011-07-01 15:40:20 -07:00			`public abstract async string? get_folder_delimiter_async(string toplevel,`
			`Cancellable? cancellable = null) throws Error;`
Persist messages locally: #3742 This completes the heavy lifting of persisting messages locally. The strategy is that the local database may be sparsely populated, both in the availability of messages in a folder and the fields of a message that is partially stored. As data is pulled from the remote server it's always stored in the database. Future requests will always go to the database first, preventing unnecessary network traffic. Also, this patch will detect when a message is stored in multiple folders on the server. The database uses soft links from the folder to the message, so the message is stored only once in the database. This technique relies heavily on the availability and validity of the Message-ID header, but we expect this to be reliable the vast majority of the time. 2011-06-23 19:07:04 -07:00			`}`

			`public interface Geary.RemoteFolder : Object, Geary.Folder {`
			`}`