File: resource_message_filter.h

package info (click to toggle)
chromium 139.0.7258.127-2
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 6,122,156 kB
  • sloc: cpp: 35,100,771; ansic: 7,163,530; javascript: 4,103,002; python: 1,436,920; asm: 946,517; xml: 746,709; pascal: 187,653; perl: 88,691; sh: 88,436; objc: 79,953; sql: 51,488; cs: 44,583; fortran: 24,137; makefile: 22,147; tcl: 15,277; php: 13,980; yacc: 8,984; ruby: 7,485; awk: 3,720; lisp: 3,096; lex: 1,327; ada: 727; jsp: 228; sed: 36
file content (51 lines) | stat: -rw-r--r-- 1,970 bytes parent folder | download | duplicates (9)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
// Copyright 2015 The Chromium Authors
// Use of this source code is governed by a BSD-style license that can be
// found in the LICENSE file.

#ifndef PPAPI_PROXY_RESOURCE_MESSAGE_FILTER_H_
#define PPAPI_PROXY_RESOURCE_MESSAGE_FILTER_H_

#include "base/memory/ref_counted.h"
#include "ppapi/proxy/ppapi_proxy_export.h"

namespace IPC {
class Message;
}

namespace ppapi {
namespace proxy {
class ResourceMessageReplyParams;

// A ResourceMessageFilter lives on the IO thread and handles messages for a
// particular resource type. This is necessary in some cases where we want to
// reduce latency by doing some work on the IO thread rather than having to
// PostTask to the main Pepper thread.
//
// Note: In some cases we can rely on a reply being associated with a
// particular TrackedCallback, in which case we can dispatch directly to the
// TrackedCallback's thread. See ReplyThreadRegistrar. That should be the first
// choice for avoiding an unecessary jump to the main-thread.
//
// ResourceMessageFilter is for cases where there is not a one-to-one
// relationship between a reply message and a TrackedCallback. For example, for
// UDP Socket resources, the browser pushes data to the plugin even when the
// plugin does not have a pending callback. We can't use the
// ReplyThreadRegistrar, because data may arrive when there's not yet a
// TrackedCallback to tell us what thread to use. So instead, we define a
// UDPSocketFilter which accepts and queues UDP data on the IO thread.
class PPAPI_PROXY_EXPORT ResourceMessageFilter
    : public base::RefCountedThreadSafe<ResourceMessageFilter> {
 public:
  virtual bool OnResourceReplyReceived(
      const ResourceMessageReplyParams& reply_params,
      const IPC::Message& nested_msg) = 0;

 protected:
  friend class base::RefCountedThreadSafe<ResourceMessageFilter>;
  virtual ~ResourceMessageFilter() {}
};

}  // namespace proxy
}  // namespace ppapi

#endif  // PPAPI_PROXY_RESOURCE_MESSAGE_FILTER_H_