"Send Request.vi" should still send RPC request to handler on string error

[Electric-Spark]

It's annoying that if you feed a garabage string to the Send Request, that it can error on string parsing. So you have to add reactionary code there that mimics what you do in the "Error Receiving Command" case of the server.

Ideally, Send Request would still send the request which would trip the handling in the server. Seems like a double need for error checking without it. Unfortunantly, this is likely a breaking change since I'm guessing most folks have worked around this like I have and would now get two responses if the Send Request started sending it down :(

[Electric-Spark]

Although I guess you could also argue that the ID value of async would then be invalid, which wouldn't make sense...so maybe the duplication is necessary.

[tannerblair]

Your second comment is why I haven't solved this problem, but I'm open to suggestions on how to more elegantly handle this case while maintaining the decoupling of the two processes.