Oliver Vogel wrote:
I agree with Olli -- the base use needs to be bullet-proof simple. Developers who need something special (and who have the ability) can delve deeper into the object for more power.@chris I think, what you write sounds good, BUT (sorry for that BUT ;-) We have to pay attention that the Client is not to hard to understand (and so to use).I think, it is not a good idear to set too much "properties" to get the class working. It is good to have these possibilities. But the class must work with something like (pseudo) ac = new QxAJAXClient(); ac.addBinding(<<url>>,<<Server-function>>,<<Client-function>>); ac.doIt(<<data>>); -- or -- ac = new QxAJAXClient(<<url>>); ac.doIt(<<data>>, <<Client-function>>); In this case we must have default-methods to do everything needet to let the class work. If one has to do more work, he will not use the class (if he has to do something special, i thing it is no problem to have more sophisticated work - but not for the default - case) I don't matter if we named the function "addBinding" or "doIt" ore something other ;-) Olli My 2 cents. -Chris ******************** Chris Banford [EMAIL PROTECTED] bSoftware www.bsoft.ch 078 609.20.34 Skype: zermattchris Zermatt, Switzerland ******************** |
begin:vcard fn:Chris Banford n:Banford;Chris org:bSoftware adr:Luchernstrasse 6;;Haus Olympia;Zermatt;;3920;Switzerland email;internet:[EMAIL PROTECTED] tel;work:+41 (0)78 609 2034 url:http://www.bsoft.ch version:2.1 end:vcard
