If someone registers for my app this registration could include the IP address, therefore the backend could know the state in which the user is.
Based on this information localization of E-Mail templates could be done.
(e.g. a template could also have a filter)
Hi Jens,
Good idea. We’ll add more information about the request in the InvocationContext so it can be implemented using custom business logic. It could fit quite nicely as a service enhancer available through the Marketplace.
Regards,
Mark
Adding the IP address of the “client” or whatever it is to the InvocationContext might also be useful in different contexts.
Maybe I’d like to blacklist some IP / range / state…
I created a ticket to pass on all available request headers. The IP address may be present in one of these: Remote_Address, X_Forwarded_For.