push/pull path enhancement

Currently, the implemented push/pull function requires user to enter full path 
of a file in order to push/pull file.

For example:
1. Instead of,
push('data.jar', '/data/local/tmp')
you need to enter
push('data.jar', '/data/local/tmp/data.jar')

2. Instead of,
pull('/data/local/tmp/test.jar', '')
you need to enter
pull('/data/local/tmp/test.jar', 'test.jar')

The thing is not it's hard to know where the remote file is a directory or file 
or not exists before we push the file, we can only know when the error occurs.

Possible solution:
Because the design of ddmlib, there is no way to construct a 
SyncService.FileEntry with predetermined path. Instead, you must first find 
node, list every children under that node then find the node you want, so on 
and so forth. But this would be time consuming and would break the current 
architecture of ddmlib. Personally I'll prefer leave it the way it is, but 
consider it maybe an inconvenience to the user.

Please advise.

Original issue reported on code.google.com by aitjcize on 29 Jul 2011 at 3:30

leijian / aster

push/pull path enhancement #3