Define remote calls in interface modules

Discussion in 'Developers' Forum' started by Schnacki, Jul 28, 2013.

  1. Schnacki

    Schnacki New Member

    Hello

    I'm currently researching options for an enhancement to ISPConfig.

    I'm not 100% clear on the details, but I had the idea, that this might be solved via a combination of an interface module and a remote API.

    Unfortunately it seems, that the possible calls for the remote API are hard coded in the file
    Code:
    interface/lib/classes/remote.inc.php
    Did I miss something, or is it currently not possible to extend the remote api without hacking (at least) this file?

    Regards,
    Jan
     
  2. Croydon

    Croydon Member Howtoforge Staff Moderator HowtoForge Supporter ISPConfig Developer

    I don't really get your point :)

    All remote api functions are in the remoting library and that's how it is intended. Why would you want to mix remote API with other interface things? It's a completely different thing.
     
  3. till

    till Super Moderator Howtoforge Staff HowtoForge Supporter ISPConfig Developer

    Combining interface modules with remote api call does not make much sense as Crouydon pointed out.

    The remote api is a normal php class, so you can extend it like any other calls:

    - create a new file in the remote folder.
    - include the current remote class.
    extend the curent remote class like this:

    class custom_remote extends remoting {
    ....

    }

    then create soap server socket for it and call this new endboint in your remote client script.
     
  4. Schnacki

    Schnacki New Member

    I do not plan to use the remote API in my module. I was thinking about providing functionality within ISPConfig that can then be accessed via the remote API.

    Maybe I'm on the wrong path here, but currently this looks like a good path for me.

    I'll try to understand what Till wrote (or better: what he implied because it's obvious for him) now.

    Thanks for the hints. :)
     

Share This Page