Naming Conflict For Google Base and BaseServiceCL

[GoogleCodeExporter]

The current naming of the googlecl.service.BaseServiceCL will interfere with a 
future Google Base Service class. 

As all of the current services follow this naming convention:

BloggerServiceCL

It would be logical to assign a new Google Base Service with BaseServiceCL. But 
this is already used by the parent class.

I would suggest renaming googlecl.service.BaseServiceCL to 
googlecl.service.BasicServiceCL.

I've attached a patch that covers all the files in the src/ directory.

Original issue reported on code.google.com by joseph.a...@gmail.com on 21 Jun 2010 at 5:43

Attachments:

• BasicServiceCL.patch

[GoogleCodeExporter]

While this issue brings up a valid point, it's only necessary if Google Base 
gets incorporated into GoogleCL. I'm marking this WontFix for now, but thanks 
for bringing it up.

(I did actually read and consider this patch, since I wasn't aware of Google 
Base, but never got around to responding to it until now. Thanks for the 
heads-up!)

Original comment by tom.h.mi...@gmail.com on 5 Oct 2010 at 4:08

• Changed state: WontFix