Hi there, have you ever considered/designed the library to be used in a web server, for tracking server-side events?
The current design and the use of statics seems to only work for single-user applications (ie: client apps), but in a web scenario you would need an AmplitudeService per request – since the identification of a user would need to be different per request rather than static/singleton.
Just wondering if this is at all retrofittable or whether it would need to be majorly redesigned to do so.
Hi there, have you ever considered/designed the library to be used in a web server, for tracking server-side events?
The current design and the use of statics seems to only work for single-user applications (ie: client apps), but in a web scenario you would need an AmplitudeService per request – since the identification of a user would need to be different per request rather than static/singleton.
Just wondering if this is at all retrofittable or whether it would need to be majorly redesigned to do so.