Replace ripple_path_find with path_find in paths snippet

[justinr1234]

No description provided.

[JST5000]

Closing since ripple_path_find is a fine similar request to send

[mvadari]

It is recommended that people use path_find instead of ripple_path_find especially when you have a WS client (like xrpl.js). IMO this should be reopened, since snippets should be promoting best practices.

[ckeshava]

@mvadari Both the commands path_find and ripple_path_find are supported by JSON-RPC protocol. Why is path_find recommended for WebSocket connections ? (apart from having to subscribe to continuous stream of updates)

The code-paths used by ripple_path_find and path_find requests culminate in https://github.com/XRPLF/rippled/blob/2f432e812cb773048530ebfaf2e0e6def51e3cc2/src/xrpld/app/paths/PathRequest.cpp#L244 . A substantial portion of their logic is performed by this common function.

[mvadari]

Both the commands path_find and ripple_path_find are supported by JSON-RPC protocol. Why is path_find recommended for WebSocket connections ? (apart from having to subscribe to continuous stream of updates)

path_find is recommended over ripple_path_find because paths change every ledger and ripple_path_find only returns the results once.

From the docs for ripple_path_find:

However, the results tend to become outdated as time passes. Instead of making multiple calls to stay updated, you should instead use the path_find method to subscribe to continued updates where possible.