[EDIT] Three anomalies

Hey Tommaso,

I didn't test this, but my workmate says that limelm.pkey.activity reports the deactivations done trough the server interface but not those done trough the client and the dll.

I'll double check this later today, but the function should return all deactivations.

The other strange thing is that all the activation that I tried today has always been reported with an IP of 0.0.0.0. Is this normal?

This isn't normal. Our server filters out what it sees as bad IP addresses -- we'll look into why you're getting 0.0.0.0.

But the IP addresses aren't used for anything other than display purposes.

Thank you Wyatt, we are waiting for the modifications.

In the meantime my workmates noticed that limelm.pkey.activity method is giving back just the last activation and deactivation and both with wrong datetime.

At the same time he is wondering how to use the created, revoked, activation, deactivation optional parameters, because whenever he is putting true or false nothing is changing for him.

We'll look into this. Just note that the date time is in eastern time (New York time). We'll be making the timezone customizable in about a month.

Yes yes, the eastern time matter doesn't matter... 😛 We are just worried about the equal datetimes and the fact that we are seeing just the lasts.

About the ip, my ip is incorrect, my workmate from the same office is correct. The only two differences is that he is connected to one more switch before reaching the same router and I am on a VM he is on a physical machine.

Regarding the activity API, everything is working fine here. All the parameters work correctly (created, revoked, activation, deactivation, etc.). You should note that LimeLM doesn't repeat data. That is, if you created a product key within the date range you specified and you also revoked (or unrevoked) the product key, then LimeLM will still only show the product key once. It won't show it once as "you created it on X date and revoked it on Y date". Use the "created" and "revoked" attributes.

Does that make sense?

We're still looking into the 0.0.0.0 IP bug, though.

In the meantime my workmates noticed that limelm.pkey.activity method is giving back just the last activation and deactivation and both with wrong datetime.

Make sure the date range provided is wide enough. Also make sure you factor in the New York time difference.