You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@turbine.apache.org by John Thorhauer <jo...@zenplex.com> on 2001/03/01 14:58:07 UTC
FileTransfer and TurbineXmlRpcService
Currently the FileTransfer class catches any errors that occur and returns
void. I would like to make a change so that FileTransfer and then
TurbineXmlRpcService get, remove, and send methods will return a boolean true
if there is no error or false if an error ocurred.
Any comments?
John
--
********************************
** John Thorhauer
** john@zenplex.com
** take a look at:
** http://tambora.zenplex.org
** http://www.zenplex.org
** http://www.zenplex.com
********************************
Re: FileTransfer and TurbineXmlRpcService
Posted by John Thorhauer <jo...@zenplex.com>.
On Thursday 01 March 2001 19:49, Jason van Zyl wrote:
>
> We could return a boolean, or would it be more in keeping to
> catch an exception?
Throwing the exception works for me and is probably more useful in the long
run.
>The error should be reported, I'm just
> wondering if we should follow any patterns that have been
> layed down in Turbine already.
>
Should it just throw the current exception and leave it up to the developer
to catch it or should it create a TurbineException? I dont know if there is
a preference here or not.
John
--
********************************
** John Thorhauer
** john@zenplex.com
** take a look at:
** http://tambora.zenplex.org
** http://www.zenplex.org
** http://www.zenplex.com
********************************
Re: FileTransfer and TurbineXmlRpcService
Posted by Jason van Zyl <jv...@periapt.com>.
On Thu, 1 Mar 2001, John Thorhauer wrote:
> Currently the FileTransfer class catches any errors that occur and returns
> void. I would like to make a change so that FileTransfer and then
> TurbineXmlRpcService get, remove, and send methods will return a boolean true
> if there is no error or false if an error ocurred.
>
> Any comments?
We could return a boolean, or would it be more in keeping to
catch an exception? The error should be reported, I'm just
wondering if we should follow any patterns that have been
layed down in Turbine already.
jvz.