My application uses typica separately from lifeguard as well. Assuming
I use the typica jar bundled with lifeguard, some of the traffic will
be misidentified as coming via lifeguard. And, conversely, if I use
the typica jar from the typica distribution, then the typica-via-
lifeguard traffic will not be identified as such.
Just wanted to make sure you're aware of this.
On Aug 6, 6:47 pm, "David Kavanagh" <
dkavan...@gmail.com> wrote:
> I have been keeping typica updated in lifeguard. It is currently the
> 1.3 release, but has a special version string because Amazon wanted to
> be able to tell how much SQS traffic was generated from lifeguard, so
> the user-agent indicates typica-1.3-lg
>
> David
>