support HTTP timeouts (or other request options)

[jbcpollak]

I would like to be able to control the request timeout from the client side, but it appears loopback-connector-remote does not expose this functionality - It looks like strong-remoting doesn't allow the user to add fields to the request options object, that might be by design, but I think it would be useful to expose timeout and possibly a few other fields.

The lack of a timeout is causing me problems right now - the remote call doesn't timeout in a reasonable time, and my unit test actually times out before the call does, so I couldn't even see the root cause of the error, just that the test died. Now that I've figured that out, I'd like to set my timeout to be ~5 seconds (unit test timeout is 15 seconds), so that in the future this would be catchable.

[richardpringle]

@jbcpollak, would you want this feature to be connector-remote specific? Or do you think it should be a part of strong-remoting? I think the change would have to be made in strong-remoting, might be better to open up an issue in there or we can leave this issue open and cross-link the two.

Open a new issue in strong-remoting and mention me in the description please.

[jbcpollak]

As an end user I'm interested in the feature being exposed here, but I do agree it should probably be implemented in strong-remoting. Honestly as a user of Loopback, I don't really get what the utility of strong-remoting is outside of Loopback.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[jbcpollak]

I still think this is important and shouldn't be closed.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[richardpringle]

@kjdelisle, calm that stalebot down! haha I'm with @jbcpollak on this one, I think this feature shoud be in here.