The protocol is something we designed and based on several google technologies:
1. Bottom layer is p2p connection established by libjingle, this can be udp, tcp or relay through google. 2. We use PseudoTcp implementation in libjingle to provide reliable connection. 3. On top of that is SSL connection. 4. protobuf is used for structured data and framing. 5. Graphics is encoded using VP8.
Alpha
2011年10月8日11:09 Sankar P <sankar.curios...@gmail.com>:
> The protocol is something we designed and based on several google > technologies: > 1. Bottom layer is p2p connection established by libjingle, this can be udp, > tcp or relay through google. > 2. We use PseudoTcp implementation in libjingle to provide reliable > connection. > 3. On top of that is SSL connection. > 4. protobuf is used for structured data and framing. > 5. Graphics is encoded using VP8. > Alpha > 2011年10月8日11:09 Sankar P <sankar.curios...@gmail.com>:
>> Hi,
>> I recently saw an extension from google for accessing remote desktops >> within intranet by chromium team -
On Sat, Oct 8, 2011 at 8:45 AM, Sankar P <sankar.curios...@gmail.com> wrote: > ah okay. thanks. Is there a RFC (or some page) where this is > documented in detail ?
No, there is no spec for the protocol yet, but we will probably publish something as the protocol matures. The implementation is open-source, sources are in chromium SVN: http://src.chromium.org/viewvc/chrome/trunk/src/remoting/
> On Sat, Oct 8, 2011 at 9:03 PM, Alpha (Hin-Chung) Lam <hc...@google.com> > wrote: > > The protocol is something we designed and based on several google > > technologies: > > 1. Bottom layer is p2p connection established by libjingle, this can be > udp, > > tcp or relay through google. > > 2. We use PseudoTcp implementation in libjingle to provide reliable > > connection. > > 3. On top of that is SSL connection. > > 4. protobuf is used for structured data and framing. > > 5. Graphics is encoded using VP8. > > Alpha > > 2011年10月8日11:09 Sankar P <sankar.curios...@gmail.com>:
> >> Hi,
> >> I recently saw an extension from google for accessing remote desktops > >> within intranet by chromium team -
On Sun, Oct 9, 2011 at 12:07 AM, Sergey Ulanov <serg...@chromium.org> wrote: > On Sat, Oct 8, 2011 at 8:45 AM, Sankar P <sankar.curios...@gmail.com> wrote:
>> ah okay. thanks. Is there a RFC (or some page) where this is >> documented in detail ?
> No, there is no spec for the protocol yet, but we will probably publish > something as the protocol matures. The implementation is open-source, > sources are in chromium SVN: > http://src.chromium.org/viewvc/chrome/trunk/src/remoting/
Thanks. I will have a look. I will try to implement this for telepathy (if time permits) so that we can access a remote chrome browser from any telepathy client and not just another instance of chrome.
On an unrelated side note, I am tempted to ask those who complained nothing except core-browsing should be included when I proposed telepathy integration :-) However, I understand the rationale behind this feature and will keep quiet :)
>> On Sat, Oct 8, 2011 at 9:03 PM, Alpha (Hin-Chung) Lam <hc...@google.com> >> wrote: >> > The protocol is something we designed and based on several google >> > technologies: >> > 1. Bottom layer is p2p connection established by libjingle, this can be >> > udp, >> > tcp or relay through google. >> > 2. We use PseudoTcp implementation in libjingle to provide reliable >> > connection. >> > 3. On top of that is SSL connection. >> > 4. protobuf is used for structured data and framing. >> > 5. Graphics is encoded using VP8. >> > Alpha >> > 2011年10月8日11:09 Sankar P <sankar.curios...@gmail.com>:
>> >> Hi,
>> >> I recently saw an extension from google for accessing remote desktops >> >> within intranet by chromium team -
This is not part of the core browser, as you can see, it is an extension. It is part of the code base for convenience and due to base dependencies, I guess.
On Sun, Oct 9, 2011 at 07:25, Sankar P <sankar.curios...@gmail.com> wrote: > On Sun, Oct 9, 2011 at 12:07 AM, Sergey Ulanov <serg...@chromium.org> > wrote: > > On Sat, Oct 8, 2011 at 8:45 AM, Sankar P <sankar.curios...@gmail.com> > wrote:
> >> ah okay. thanks. Is there a RFC (or some page) where this is > >> documented in detail ?
> > No, there is no spec for the protocol yet, but we will probably publish > > something as the protocol matures. The implementation is open-source, > > sources are in chromium SVN: > > http://src.chromium.org/viewvc/chrome/trunk/src/remoting/
> Thanks. I will have a look. I will try to implement this for telepathy > (if time permits) so that we can access a remote chrome browser from > any telepathy client and not just another instance of chrome.
> On an unrelated side note, I am tempted to ask those who complained > nothing except core-browsing should be included when I proposed > telepathy integration :-) However, I understand the rationale behind > this feature and will keep quiet :)
> Sankar
> >> On Sat, Oct 8, 2011 at 9:03 PM, Alpha (Hin-Chung) Lam <hc...@google.com
> >> wrote: > >> > The protocol is something we designed and based on several google > >> > technologies: > >> > 1. Bottom layer is p2p connection established by libjingle, this can > be > >> > udp, > >> > tcp or relay through google. > >> > 2. We use PseudoTcp implementation in libjingle to provide reliable > >> > connection. > >> > 3. On top of that is SSL connection. > >> > 4. protobuf is used for structured data and framing. > >> > 5. Graphics is encoded using VP8. > >> > Alpha > >> > 2011年10月8日11:09 Sankar P <sankar.curios...@gmail.com>:
> >> >> Hi,
> >> >> I recently saw an extension from google for accessing remote desktops > >> >> within intranet by chromium team -
On Sat, Oct 8, 2011 at 11:50 PM, PhistucK <phist...@gmail.com> wrote: > This is not part of the core browser, as you can see, it is an extension. > It is part of the code base for convenience and due to base dependencies, I > guess.
Currently the client code is a pepper plugin built into the browser (host is a separate NPAPI plugin). Our long-term plan is to separate this code from the browser and move it to a separate NaCl plugin installed as part of the web app, but this is contingent on implementation of some networking API for NaCl.
> On Sun, Oct 9, 2011 at 07:25, Sankar P <sankar.curios...@gmail.com> wrote:
>> On Sun, Oct 9, 2011 at 12:07 AM, Sergey Ulanov <serg...@chromium.org> >> wrote: >> > On Sat, Oct 8, 2011 at 8:45 AM, Sankar P <sankar.curios...@gmail.com> >> wrote:
>> >> ah okay. thanks. Is there a RFC (or some page) where this is >> >> documented in detail ?
>> > No, there is no spec for the protocol yet, but we will probably publish >> > something as the protocol matures. The implementation is open-source, >> > sources are in chromium SVN: >> > http://src.chromium.org/viewvc/chrome/trunk/src/remoting/
>> Thanks. I will have a look. I will try to implement this for telepathy >> (if time permits) so that we can access a remote chrome browser from >> any telepathy client and not just another instance of chrome.
>> On an unrelated side note, I am tempted to ask those who complained >> nothing except core-browsing should be included when I proposed >> telepathy integration :-) However, I understand the rationale behind >> this feature and will keep quiet :)
>> Sankar
>> >> On Sat, Oct 8, 2011 at 9:03 PM, Alpha (Hin-Chung) Lam < >> hc...@google.com> >> >> wrote: >> >> > The protocol is something we designed and based on several google >> >> > technologies: >> >> > 1. Bottom layer is p2p connection established by libjingle, this can >> be >> >> > udp, >> >> > tcp or relay through google. >> >> > 2. We use PseudoTcp implementation in libjingle to provide reliable >> >> > connection. >> >> > 3. On top of that is SSL connection. >> >> > 4. protobuf is used for structured data and framing. >> >> > 5. Graphics is encoded using VP8. >> >> > Alpha >> >> > 2011年10月8日11:09 Sankar P <sankar.curios...@gmail.com>:
>> >> >> Hi,
>> >> >> I recently saw an extension from google for accessing remote >> desktops >> >> >> within intranet by chromium team -
