I a little new to all of this, but I'm trying to build a SaaS-like application where an ASP.NET Web API will submit transactions. I'm using the .NET SDK. I noticed this code:
ApiOperationBase<ANetApiRequest, ANetApiResponse>.MerchantAuthentication = new merchantAuthenticationType() { name = ApiLoginID, ItemElementName = ItemChoiceType.transactionKey, Item = ApiTransactionKey, };
When I dig into the GitHub code, it looks like this will end up as static variables somewhere and that means they'll be shared across instances of the web site.
Do I have this right? Is there a model for an instance based version where I can run multiple simultaneous requests without overlapping the ApiLoginId?
Sorry if this is completely misguided, but it's bothering me at an early stage of the design.
TIA - Bill
Solved! Go to Solution.
04-20-2016 11:47 AM - edited 04-20-2016 11:47 AM
Nevermind. I did some testing. Looks like they aren't shared after all. Just not familiar with that constructor. :(
04-20-2016 02:25 PM
Nevermind. I did some testing. Looks like they aren't shared after all. Just not familiar with that constructor. :(
04-20-2016 02:25 PM