summaryrefslogtreecommitdiffstats
path: root/netwerk/protocol/websocket/IPCTransportProvider.h
blob: 343d3c03801d184d32a949d6cb094f818ec9303a (plain)
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
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
/* -*- Mode: C++; tab-width: 8; indent-tabs-mode: nil; c-basic-offset: 2 -*- */
/* vim: set sw=2 ts=8 et ft=cpp : */
/* 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 mozilla_net_IPCTransportProvider_h
#define mozilla_net_IPCTransportProvider_h

#include "nsISupportsImpl.h"
#include "mozilla/net/PTransportProviderParent.h"
#include "mozilla/net/PTransportProviderChild.h"
#include "nsIHttpChannelInternal.h"
#include "nsITransportProvider.h"

/*
 * No, the ownership model for TransportProvider is that the child object is
 * refcounted "normally". I.e. ipdl code doesn't hold a strong reference to
 * TransportProviderChild.
 *
 * When TransportProviderChild goes away, it sends a __delete__ message to the
 * parent.
 *
 * On the parent side, ipdl holds a strong reference to TransportProviderParent.
 * When the actor is deallocatde it releases the reference to the
 * TransportProviderParent.
 *
 * So effectively the child holds a strong reference to the parent, and are
 * otherwise normally refcounted and have their lifetime determined by that
 * refcount.
 *
 * The only other caveat is that the creation happens from the parent.
 * So to create a TransportProvider, a constructor is sent from the parent to
 * the child. At this time the child gets its first addref.
 *
 * A reference to the TransportProvider is then sent as part of some other
 * message from the parent to the child. For example in the
 * PFlyWebPublishedServer.WebSocketRequest message.
 *
 * The receiver of that message can then grab the TransportProviderChild and
 * without addreffing it, effectively using the refcount that the
 * TransportProviderChild got on creation.
 */

class nsISocketTransport;
class nsIAsyncInputStream;
class nsIAsyncOutputStream;

namespace mozilla {
namespace net {

class TransportProviderParent final : public PTransportProviderParent
                                    , public nsITransportProvider
                                    , public nsIHttpUpgradeListener
{
public:
  TransportProviderParent();

  NS_DECL_ISUPPORTS
  NS_DECL_NSITRANSPORTPROVIDER
  NS_DECL_NSIHTTPUPGRADELISTENER

  void ActorDestroy(ActorDestroyReason aWhy) override {};

private:
  ~TransportProviderParent();

  void MaybeNotify();

  nsCOMPtr<nsIHttpUpgradeListener> mListener;
  nsCOMPtr<nsISocketTransport> mTransport;
  nsCOMPtr<nsIAsyncInputStream> mSocketIn;
  nsCOMPtr<nsIAsyncOutputStream> mSocketOut;
};

class TransportProviderChild final : public PTransportProviderChild
                                   , public nsITransportProvider
{
public:
  TransportProviderChild();

  NS_DECL_ISUPPORTS
  NS_DECL_NSITRANSPORTPROVIDER

private:
  ~TransportProviderChild();
};

} // namespace net
} // namespace mozilla

#endif