Details

    • Type: New Feature New Feature
    • Status: Resolved Resolved
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 0.5.0, 0.6.0, 0.6.1, 0.6.1.1
    • Fix Version/s: 0.7.0
    • Component/s: Networking
    • Labels:
      None
    • Environment:
      All

      Description

      We need to re-implement XML-RPC logins (the XML-RPC library is already shipping as a dependency of GridProxy, so nothing new there). Ideally, XML-RPC and LLSD would both be supported through a Settings bool, with XML-RPC set as the default.

        Issue Links

          Activity

          Hide
          Jim Radford added a comment -

          I've got this working, just need to finish merging some structs and mapping XML-RPC field names

          Show
          Jim Radford added a comment - I've got this working, just need to finish merging some structs and mapping XML-RPC field names
          Hide
          Jim Radford added a comment -

          This is now added back to the library.

          Show
          Jim Radford added a comment - This is now added back to the library.
          Hide
          Jim Radford added a comment -

          This change modifies the LoginResponseData struct to use Common Types supported by XML-RPC.NET, which means for example UUIDs are stored as a string and must be Parsed into an actual UUID to be used for most things.

          We should come to some sort of decision if this is the direction to go, or if it would possibly be better implementing separate classes for XML-RPC and LLSD. From a workload point of view I'm not really sure it is much of a difference, either we use one struct to store custom types and convert them to string represenations for LLSD, or we store them in common types and convert them into their actual custom type.

          Would like to hear some feedback from other devs on this.

          Show
          Jim Radford added a comment - This change modifies the LoginResponseData struct to use Common Types supported by XML-RPC.NET, which means for example UUIDs are stored as a string and must be Parsed into an actual UUID to be used for most things. We should come to some sort of decision if this is the direction to go, or if it would possibly be better implementing separate classes for XML-RPC and LLSD. From a workload point of view I'm not really sure it is much of a difference, either we use one struct to store custom types and convert them to string represenations for LLSD, or we store them in common types and convert them into their actual custom type. Would like to hear some feedback from other devs on this.

            People

            • Assignee:
              Jim Radford
              Reporter:
              John Hurliman
            • Votes:
              1 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: