Thanks for all the suggestions! Given that the Perl module will, for now, be more than just a web client (a portion of it will need to gather data by parsing log files) I think I will go with App::Spoor - with the intent to break off the part that has the webservice functionality into Webservice::Spoor - I will hold off on Spoor:: until I am sure it is not just hurbis talking :).
Thanks again! On Wed, 23 Jan 2019 at 21:02, Doug Bell <d...@preaction.me> wrote: > > On Jan 23, 2019, at 9:16 AM, Rory McKinley <rorymckin...@capefox.co> > wrote: > > > > I am developing a hosted application called Spoor. I would like to build > a Perl client module for this application that will (amongst other things) > interact with the Spoor Api. > > > > My current inclination is to call the module Spoor::Client, but that > will mean that I will be creating a new top-level name which I know is > discouraged. Is there a suitable top-level name that I could host my client > under, or would grabbing the Spoor name be ok under these circumstances? > > If it's a web service, I'd say use WWW:: or WebService::. If it's an OSI > Layer 7 protocol like HTTP, I'd go with Net::. If all else fails, > API::Spoor wouldn't be a terrible idea. > > > Doug Bell > d...@preaction.me > -- Rory McKinley Director Cape Fox Consulting (Pty) Ltd Registration No: 2015/388067/07 Director(s): R McKinley
