Developer forum

When a user log on, the Dynamicweb.Notifications.Standard.User.OnExtranetLogin notification is thrown, so you can use that to do the logging.

Hi

You can also find the information in the statistics database. Statv2session table, field Statv2SessionExtranetUserID - if it is more than 0, you can find the user from AccessUser table.

Perfecto - grazie :o)

Would Dynamicweb.Notifications.Standard.User.OnExtranetLogin notification also be a good place to have login/connect to a webservice ?

Ex:

The client have a shop where logged in users can buy stuff.

They want to get prices from another system and also place orders direcly in their ERP system.

The ERP vender have a ready to go .NET API where i can connect to using userid/password.

But as i dont want to connect for each request (takes too much time), i want to connect once for all in the beginning.

Get the meaning ?

And what will i have to take in account especially if this connection stays up ?

/Lars

I'd say that it would depend on the amount of data. If you client has a modest number of products, sure, why not. But this runs only once, so every time a page is requested I'd check that custom data has been fetched and cached and attemt to load the data if they are not present.

But if your client has 100.000 products, and you need to fetch and store prices for all, you might want to look at the Dynamicweb.Notifications.eCommerce.ProductList notification instead. This allows you manipulate with the list of products currently displayed, so you can limit the call to the ERP to only concern these products.

What do you mean by the last question "connection stays up"?