Announcement

Collapse
No announcement yet.

Ubuntu's Mir Works Towards Screen-Casting Support

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • #16
    Originally posted by GraysonPeddie View Post
    Ugh! Here comes paranoia and NSA...
    Here comes fact free blissful ignorance

    Comment


    • #17
      I wonder if this has anything to do with screen casting.

      Comment


      • #18
        Originally posted by jakubo View Post
        therefore open hardware..?
        That may be a part of it... but where do you trust it to be manufactured? some of the tools from the NSA oresentation were tiny, so they can still be planted onto the motherboards etc.

        and even with secure computers, internet secrecy is another matter.

        even with the new perfect forward security stuff, as the relevant data may be stored for upto 15 years, it just means one additional step to infiltration and lack of privacy instead of all data always being unsecure "by default".

        (Another question here is if everyone is at it (NSA is. NSA accuses the chinese of doing similar things...), who is less damaging? So in the US is it "better" to use chinese hardware because they have less interest in you? and vice versa, in China, US hardware?)

        Comment


        • #19
          Originally posted by You- View Post
          That may be a part of it... but where do you trust it to be manufactured?
          There are fabs outside US and China ya know.

          Comment


          • #20
            Originally posted by Pajn View Post
            Mir and Wayland work in different ways.
            Wayland is no display server, it's just a protocol to describe how programs should talk to the compositor.
            Mir is a display server and the compositor is a client that connects to Mir. With this approach you can redirect
            full-screen apps directly to the display server which gains some performance but gives the compositor less control.

            And yeah what this is about is an interface to provide the rendered frames to a client. If the client uses this for
            creating a screen cast video or implementing RDP doesn't concern Mir.
            But wayland compositors should bypass compositing for fullscreen frames. There should be no overhead at all... at least if the client uses the wl_fullscreen_shell protocol extension, if I'm not mistaken.

            Comment


            • #21
              Originally posted by newwen View Post
              But wayland compositors should bypass compositing for fullscreen frames. There should be no overhead at all... at least if the client uses the wl_fullscreen_shell protocol extension, if I'm not mistaken.
              Yes of course. For performance the same levels should be reachable with both approaches.
              I just explained why Mir needs explicit support for this. A Wayland compositor could do
              this without any support in the Wayland protocol (however support in the protocol would
              be preferable (and may exist) for having compatibility between different compositors).

              Comment


              • #22
                Originally posted by justmy2cents View Post
                screencasting in display server? shouldn't this be in compositor? both wayland and mir already treat clients like sinks if i understand correctly, which would also mean you could enable screencasting in any compositor simply by using infrastructure they work on
                I'm not sure about Mir but Wayland calls for the compositor to be the display server. That was one of the big motivating factors behind Wayland: to have the display server to be transform aware of the windows so no unneeded hops between the thing doing the transforms and the thing serving the final image.

                Comment

                Working...
                X