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
> On Jan 23, 2019, at 9:16 AM, Rory McKinley 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
There's APP:: - e.g. APP::Spoor::API & APP::Spoor::Client
On 23-Jan-19 10:16, Rory McKinley wrote:
> Hello
>
> 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.
>
>
Hello
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