You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
the new connection uri way of connecting to wdt should be the only optional parameter without requiring a --
ideally we should be able to tell from the url itself maybe if this is sender or receiver yet allow to pass one to the other (the 2 goals conflicts)
The text was updated successfully, but these errors were encountered:
ldemailly
changed the title
make connection uri read as either command line parameter (without --option)
make connection uri read as either command line parameter (without --option) or stdin (for receiver | sender)
Jul 23, 2015
…ver to sender
Summary: fix constructor and command line such as url can be passed from receiver to sender
closesfacebook#25, closesfacebook#9, progress on facebook#16
note: there is an incompatible change that you must specify a -transfer_id if you aren't going to use the URL as the default behavior is now to generate a unique id on the receiver with the expectations the url is used on the sender to connect (which is what the wdt_e2e_simple_test.sh demonstrates) but if you use the old style command line you must now specify the same non empty -transfer_id on both side
Reviewed By: @nikunjy
Differential Revision: D2289794
the new connection uri way of connecting to wdt should be the only optional parameter without requiring a --
ideally we should be able to tell from the url itself maybe if this is sender or receiver yet allow to pass one to the other (the 2 goals conflicts)
The text was updated successfully, but these errors were encountered: