Oleg Kalnichevski wrote: > On Sun, 2007-01-14 at 20:58 +0100, Roland Weber wrote: >> Oleg Kalnichevski wrote: >> >>> True. But I somehow I can't help thinking #open() and #update() might >>> suffice. Why not use #open() / #update() instead of #prepare / #open()? >> Ah, I get the idea. Modal behavior of open(). >> I didn't think of that because it means calling >> open() with a socket that is not open :-) > > This is the reason why I personally prefer 'bind'/'rebind' semantics to > 'open/'update'.
Make sure to change the method names accordingly in your patch. There's HttpConnection.isOpen(), which wouldn't match with an open() method that does not actually open the connection. But I'm afraid we'd need an isBound() method to determine whether a call to update/rebind is permissible, which would nullify the advantage of loosing the prepare() method. Btw, I think "announce" would be a better name than "prepare". It avoids the false assumption that preparation is mandatory. cheers, Roland --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
