HHVM Compatibility in Error?

[bartclarkson]

travis.yml indicates this is compatible with HHVM. I'm not seeing that. I'm using HHVM 3.7. PHP5-FPM works just fine. With HHVM, LoginResult just comes back with a bunch of NULL values in the array of protected values, leading me ultimately to an error from Salesforce of "Destination URL not reset. The URL returned from login must be set in the SforceService" from a subsequent request.

I'm going to mess with this a bit more. Would be nice to solve. Wondering if this is fundamentally the culprit: http://docs.hhvm.com/manual/en/soapclient.soapclient.php .

[ddeboer]

Let us know what you find!

[bartclarkson]

All righty, got it working. HHVM will not overwrite variables contained within the various mapped Result/Request classes unless they are a.) public variables,

class LoginResult
{
    public $metadataServerUrl;  // Yep.
    protected $passwordExpired;  // Nope.
    protected $sandbox;
    protected $serverUrl;
    protected $sessionId;
    protected $userId;
    protected $userInfo;

or b.) __set() is explicitly included in the given class in the following manner:

    public function __set($name, $value)
    {
        $this->{$name} = $value;
    }

In my project I set all Request/Result Class parameters as public to achieve complete bundle success with HHVM, while continuing success with PHP5-FPM.

What's the reason for setting any of the Request/Result Class parameters as protected? It's kind of a funky idea, given that a.) the setting of variables by SoapClient with PHP5-FPM obviously respects nothing, and b.) what protection are we really trying to accomplish? I more or less see the Classmap deal as a convenience and a type hinting benefit, rather than a control mechanism, so to speak.

Anyway, that's my rhyme. @ddeboer , your call. Thanks!