Hi. I think the reason was
a) People were writing clients that expected the method perform(), not
plastic.perform(), so we changed the spec to fit the implementations (it was
just tripping too many people up)
b) Worries about problems with method names with periods screwing up certain
languages. I can be reasonably sure that this issue was brought up by Al!
John
On Thu, May 1, 2008 at 12:38 PM, Mark Taylor <m.b.taylor-at-bristol.ac.uk> wrote:
> On Thu, 1 May 2008, Alasdair Allan wrote:
>
> There was a reason why PLASTIC called perform( ) rather than
>> plastic.perform( ) and I think this was it...
>>
>
> according to my implementation, at PLASTIC versions <0.4 it was
> "plastic.client.peform" and >=0.4 it was just "perform".
> I have absolutely no recollection of why - maybe that was it.
>
> The hub methods were prefixed "plastic.hub.".
>
>
> --
> Mark Taylor Astronomical Programmer Physics, Bristol University, UK
> m.b.taylor@bris.ac.uk +44-117-928-8776 http://www.star.bris.ac.uk/~mbt/<http://www.star.bris.ac.uk/%7Embt/>
>
-- Google Pittsburgh is hiring!Received on 2008-05-23Z06:55:56