gecko-dev/widget/xremoteclient/nsRemoteClient.h

63 строки
2.1 KiB
C
Исходник Обычный вид История

/* -*- Mode: IDL; tab-width: 4; indent-tabs-mode: nil; c-basic-offset: 2 -*- */
/* vim:expandtab:shiftwidth=4:tabstop=4:
*/
2012-05-21 15:12:37 +04:00
/* This Source Code Form is subject to the terms of the Mozilla Public
* License, v. 2.0. If a copy of the MPL was not distributed with this
* file, You can obtain one at http://mozilla.org/MPL/2.0/. */
#ifndef nsRemoteClient_h__
#define nsRemoteClient_h__
#include "nscore.h"
/**
* Pure-virtual common base class for remoting implementations.
*/
class nsRemoteClient
{
public:
/**
* Initializes the client
*/
virtual nsresult Init() = 0;
/**
Bug 1080319 - Remove the -remote option. r=bsmedberg The -remote option has existed essentially forever, but its usefulness is questionable: - It requires a running instance to be any useful, so any script actually using it should first do -remote 'ping()' and handle the response properly. - It is not cross-application. The remote service dispatches the -remote commands to the command line handler, and, for example, desktop b2g builds don't have handlers for -remote (although thunderbird and seamonkey do). - It is not a cross-platform option, which leads to the following point: - There are other command line ways to do the same thing (at least in Firefox), without having to jump through hoops with -remote 'ping()', because there are command line options to do those same things on non-X11 platforms. For the latter, in Firefox case: - -remote 'openURL(url)' can be replaced with firefox url - -remote 'openURL(url,new-tab)' can be replaced with firefox -new-tab url - -remote 'openURL(url,new-window)' can be replaced with firefox -new-window url - -remote 'openfile(file,...)' is the same as -remote 'openurl(file,...) so, can be replaced as above - -remote 'xfedocommand(openbrowser)' is inherited from the mozilla suite and doesn't make much sense, but can be replaced with firefox -new-window The interesting part is that without changing nsBrowserContentHandler.js, -remote still works, meaning that if people really feel strongly about -remote, they'll still be able to write an addon to bring it back. This also means this patch actually doesn't remove -remote for applications other than Firefox that do support it, although -remote 'ping()' doesn't work as expected. However, other -remote commands will now work even without a running instance.
2014-10-14 02:19:52 +04:00
* Send a complete command line to a running instance.
*
* @param aProgram This is the preferred program that we want to use
* for this particular command.
*
* @param aUsername This allows someone to only talk to an instance
* of the server that's running under a particular username. If
* this isn't specified here it's pulled from the LOGNAME
* environmental variable if it's set.
*
* @param aProfile This allows you to specify a particular server
* running under a named profile. If it is not specified the
* profile is not checked.
*
Bug 1080319 - Remove the -remote option. r=bsmedberg The -remote option has existed essentially forever, but its usefulness is questionable: - It requires a running instance to be any useful, so any script actually using it should first do -remote 'ping()' and handle the response properly. - It is not cross-application. The remote service dispatches the -remote commands to the command line handler, and, for example, desktop b2g builds don't have handlers for -remote (although thunderbird and seamonkey do). - It is not a cross-platform option, which leads to the following point: - There are other command line ways to do the same thing (at least in Firefox), without having to jump through hoops with -remote 'ping()', because there are command line options to do those same things on non-X11 platforms. For the latter, in Firefox case: - -remote 'openURL(url)' can be replaced with firefox url - -remote 'openURL(url,new-tab)' can be replaced with firefox -new-tab url - -remote 'openURL(url,new-window)' can be replaced with firefox -new-window url - -remote 'openfile(file,...)' is the same as -remote 'openurl(file,...) so, can be replaced as above - -remote 'xfedocommand(openbrowser)' is inherited from the mozilla suite and doesn't make much sense, but can be replaced with firefox -new-window The interesting part is that without changing nsBrowserContentHandler.js, -remote still works, meaning that if people really feel strongly about -remote, they'll still be able to write an addon to bring it back. This also means this patch actually doesn't remove -remote for applications other than Firefox that do support it, although -remote 'ping()' doesn't work as expected. However, other -remote commands will now work even without a running instance.
2014-10-14 02:19:52 +04:00
* @param argc The number of command-line arguments.
*
* @param argv The command-line arguments.
*
* @param aDesktopStartupID the contents of the DESKTOP_STARTUP_ID environment
* variable defined by the Startup Notification specification
* http://standards.freedesktop.org/startup-notification-spec/startup-notification-0.1.txt
*
* @param aResponse If there is a response, it will be here. This
* includes error messages. The string is allocated using stdlib
* string functions, so free it with free().
*
* @return true if succeeded, false if no running instance was found.
*
*/
virtual nsresult SendCommandLine(const char *aProgram, const char *aUsername,
const char *aProfile,
int32_t argc, char **argv,
const char* aDesktopStartupID,
char **aResponse, bool *aSucceeded) = 0;
};
#endif // nsRemoteClient_h__