Qt Forum

    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Unsolved
    1. Home
    2. Tags
    3. ipc
    Log in to post
    • All categories
    • H

      Unsolved Return remote object replica from remote call
      General and Desktop • remoteobject rpc ipc qt5 • • heitho

      1
      0
      Votes
      1
      Posts
      154
      Views

      No one has replied

    • C

      Unsolved Android AIDL in QT
      Mobile and Embedded • aidl android service ipc • • CatalinP

      1
      0
      Votes
      1
      Posts
      456
      Views

      No one has replied

    • A

      Unsolved Keeping a single instance of an applicaton
      General and Desktop • ipc lock • • ArsenArsen

      5
      0
      Votes
      5
      Posts
      975
      Views

      A

      @SGaist I have not, as I thought the project is unmaintaned and unsupported. I'll check out that implementation too since you're bringing it up though. Thanks

    • mistralegna

      Unsolved Serialize application types as QVariant with IPC
      General and Desktop • ipc qvariant serialization • • mistralegna

      1
      0
      Votes
      1
      Posts
      570
      Views

      No one has replied

    • AyushExel204

      Solved Wrong Implementation of single instance application
      General and Desktop • qlocalserver qlocalsocket ipc qtsingleapplica • • AyushExel204

      12
      0
      Votes
      12
      Posts
      3148
      Views

      jsulm

      sender() returns the pointer to the object which emitted the signal (http://doc.qt.io/qt-5.6/qobject.html#sender).
      In this case it is a pointer to QLocalSocket, so you need to cast it from QObject* to QLocalSocket* using qobject_cast

    • kshegunov

      Solved Barebone local IPC within QtCore
      General and Desktop • ipc • • kshegunov

      8
      0
      Votes
      8
      Posts
      1869
      Views

      kshegunov

      @Wieland

      QLocalSocket uses named pipes on Windows.

      Sure, I acknowledged that in my first post.

      Speaking of Linux, all these IPCs are more or less obsolete with the advent of kdbus.

      Maybe, however there are some issues with that. Kdbus is in the newest kernels only and not all distributions provide them (especially such as the stable flavor of Debian and other OS-es focused on longer release cycle/long-term support). The d-bus daemon is usually present, but not always, and as I recently found out (@SGaist pointed me to it) it's coming to Windows as a service. However without a full blown support from the core OS it may or may not prove a reasonable alternative. On the other hand, pipes are as old as computers themselves and run fine on pretty much any platform, have small overhead and are flexible solution to many such small-ish problems as mine.
      Do note, also, that from time to time a new technology claims that a more mature one will simply die out, however, it doesn't much seem to be the case. Java was supposed to "kill" C++, well it didn't happen. QML was supposed to replace the widgets - I personally find QML distasteful and still stick to the old-school C++ way and many others it seems.
      Anyway, don't take this as a rant, I'm just sharing a few observations. ;)
      Cheers!

    • L

      QLocalSocket: Send data that large 4096 bytes
      General and Desktop • qlocalsocket qlocalserver data data loss ipc windows • • lolopolosko

      8
      0
      Votes
      8
      Posts
      5185
      Views

      L

      @LuGRU
      Why not to use: QSharedMemory and You don't need to worry about message formatting.
      Because I run process with different account.
      First process run from System account and second from local account

      When I read SharedMemory in another process I have error "QSharedMemory handle doesn't exist"