1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

API support

Discussion in 'Feature Suggestions' started by KYL, Sep 4, 2017.

  1. KYL

    KYL New Member

    Hi,
    Can I ask if you interested in having an API for this software?

    I'm working in the field of sys admins, and having this software to possibly automate shutdowns and related operations would be huge. Your software is unique in that it does not rely on wifi or ethernet as the medium.

    Without an API it is pretty much impossible to script instructions, hopefully someone over there gets interested on this.
     
  2. Seungjin Lee

    Seungjin Lee Member

    Hello KYL,

    Welcome to Across Center! :)

    We have much interest in having an API for whatever useful but unfortunately are unable to find those useful features.
    Could you please tell me detailed description of those features?
    Thanks in advance.

    PS: FYI, The V2 of across will be released soon. In addition to existing V1.x features, it will support Keyboard/Mouse Sharing, Filecopy between computers and Clipboard data Synchronization via network. Though only Windows and macOS versions are released initially, we're going to start development for Linux and Android.
     
    Last edited: Sep 4, 2017
  3. KYL

    KYL New Member

    Hi Mr Lee,
    Basically I would like to use across similar to software KVM, with added automation features.

    Do you mean V2 will support keyboard mouse mirror input?
    • Mirror input - Broadcast mouse gestures and/or keyboard input to all computers simultaneously
     
  4. Seungjin Lee

    Seungjin Lee Member

    Hi,

    Unfortunately no. Do you want simply keyboard/mouse broadcasting?
    BTW, keyboard/mouse related operation won't be opened to others, since its security can be jeopardized.
     
  5. Lee Rhoads

    Lee Rhoads New Member

    Seungjin Lee,

    That's unfortunate. Until I noticed your comment above I was hoping you would consider creating a separate product from a subset of Across, some sort of Bluetooth keyboard and mouse emulation SDK. The SDK would consist of the following: Required Bluetooth keyboard and mouse emulation Windows 10 driver components from the Across product; an API DLL that interacts with those drivers and exposes an API; possibly a .NET Standard class library assembly that wraps that API; and of course some documentation (maybe a wiki on your website). The API would enable applications to do the following 4 things: 1) pair the host PC with a Bluetooth enabled Android/iOS/Windows/macOS/Linux target device in a manner where the host PC would be seen by the target device as an AES Bluetooth keyboard; 2) pair the host PC with a Bluetooth enabled Android/Windows/macOS/Linux target target device in a manner where the host PC would be seen by the target device as a Bluetooth mouse; 3) send AES encrypted keystrokes to target devices; 4) send mouse gestures to target devices. Perhaps the Bluetooth keyboard and mouse emulation Windows 10 driver components would have to be modified to prevent conflicts between the Across product and applications using the SDK. As for the security risks, couldn't Clixon protect itself from liability via an SDK license agreement?

    By the way, I have no need to broadcast keystrokes to multiple target devices simultaneously. Why would someone want to do that?


    Regards,
    Lee Rhoads
     

Share This Page