Thats a bit crappy - does mercury force you to work with Files instead
of streams?
Quite the opposite - Mercury transport itself does all the work,
including Stream Verifiers and so on, I just plug it into wagon and it
does the file put/get. Moreover - that layer ensures transactional
integrity of the put/get operations, so I can count on all-or-nothing
result (remember - it does multi-file multi-threaded transactions). That
is impossible to achieve with streams as it requires a concrete object -
File - to checks the existence of or drop in case of failure.
Problem is that wagon APIs are artificially forcing provider to open
inner details of the transfer process, that the provider is trying to
hide. This should be optional, in my opinion.
Thanks,
Oleg
Im always reminded of this blog post when it comes to those sorts of
API's
http://fishbowl.pastiche.org/2004/06/11/minipattern_the_file_stream_duality/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
