Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BC.OnResetTimeout] - Restructuring OnResetTimeout #112

Open
KhrystynaDubovyk opened this issue Nov 15, 2018 · 0 comments
Open

[BC.OnResetTimeout] - Restructuring OnResetTimeout #112

KhrystynaDubovyk opened this issue Nov 15, 2018 · 0 comments

Comments

@KhrystynaDubovyk
Copy link
Contributor

OnResetTimeout

Description:

OnResetTimeout notification should be applicable for all interfaces and HMI should send this RPC in case it needs more time to process a request received from SDL.

Detailed description:

OnResetTimeout function definition would be as follows for the BasicCommunication:

<function name="OnResetTimeout" messagetype="notification" since="X.Y">
    <description>
		HMI must send this notification to SDL for method instance for which timeout needs to be reset
    </description>	
    <param name="requestID" type="Integer" minvalue="0" maxvalue="65535" mandatory="true">	
		<description>
			Id between HMI and SDL which SDL used to send the request for method in question, for which timeout needs to be reset.
		</description>
    </param>
    <param name="methodName" type="String" mandatory="true">
		<description>
			Name of the function for which timeout needs to be reset
		</description>
    </param>
    <param name="resetPeriod" type="Integer" minvalue="0" maxvalue="1000000" mandatory="false">
		<description>
			Timeout period in milliseconds, for the method for which timeout needs to be reset.
			If omitted, timeout would be reset by defaultTimeout specified in smartDeviceLink.ini
		</description>
    </param>
</function>

Diagram:

N/A

Links:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant