Do I need an authenticator for each webwidget on my website?

[folaht]

Let’s say I have two simple webwidgets.

• A guestbook
• A blog

Does this mean that I need two seperate authoriseAndConnect methods, each having different appInfo?

And should authoriseAndConnect be called whenever the contact/guestbook page has been opened or when the website index page has been opened?

[hunterlester]

@folaht

Does this mean that I need two seperate authoriseAndConnect methods, each having different appInfo?

Not a necessity, it’s completely your choice.
Each widget can interact with the network through one app connection.

@folaht

And should authoriseAndConnect be called whenever the contact/guestbook page has been opened or when the website index page has been opened?

I’d have it called when the website index page is rendered in the browser.
Although, is the contact/guestbook page the only place that requires a network connection?
If so, then it might be ideal to only ask users to authorise the connection if they visit that page.

[folaht]

@hunterlester

Although, is the contact/guestbook page the only place that requires a network connection?

I turned contact page into a blog to make it clear I’m talking about requiring network connection on two different pages.
I just thought, ‘which two webwidgets are simplest to make that need network communication’?

Index page it is then, but that raises another question…