Prev: A2010 question regarding web app
Next: Can't open backend that is in use
From: David W. Fenton on 21 Jul 2010 13:44
Salad <salad(a)oilandvinegar.com> wrote in
news:K46dna2q5eMuRNjRnZ2dnUVZ_g-dnZ2d(a)earthlink.com:

> Although getting away from my original question on pics, what does
> one do to drive people to the app? Does on need to get involved
> with google analytics?

I don't really see using Sharepoint as a public web site, though I
guess it's theoretically possible. I am unclear on the authorization
model used by Sharepoint, though. I would have expected it to work
better on an Intranet than open to the Internet.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
From: Salad on 21 Jul 2010 14:19
David W. Fenton wrote:

> Salad <salad(a)oilandvinegar.com> wrote in
> news:K46dna2q5eMuRNjRnZ2dnUVZ_g-dnZ2d(a)earthlink.com:
>
>
>>Although getting away from my original question on pics, what does
>>one do to drive people to the app? Does on need to get involved
>>with google analytics?
>
>
> I don't really see using Sharepoint as a public web site, though I
> guess it's theoretically possible. I am unclear on the authorization
> model used by Sharepoint, though. I would have expected it to work
> better on an Intranet than open to the Internet.
>
Albert's video is an example that I expect would be open to the
internet. I guess he can answer better than I.

Yes, I can see it used internally but I don't see a reason it can be
used publicly.
From: Albert D. Kallal on 22 Jul 2010 16:02
"Salad" <salad(a)oilandvinegar.com> wrote in message
news:bvmdnRFHvKqmp9rRnZ2dnUVZ_qSdnZ2d(a)earthlink.com...

> David W. Fenton wrote:
>
>> Salad <salad(a)oilandvinegar.com> wrote in
>> news:K46dna2q5eMuRNjRnZ2dnUVZ_g-dnZ2d(a)earthlink.com:
>>>Although getting away from my original question on pics, what does
>>>one do to drive people to the app? Does on need to get involved
>>>with google analytics?
>>
>>
>> I don't really see using Sharepoint as a public web site, though I
>> guess it's theoretically possible. I am unclear on the authorization
>> model used by Sharepoint, though. I would have expected it to work
>> better on an Intranet than open to the Internet.
> Albert's video is an example that I expect would be open to the internet.
> I guess he can answer better than I.
>
> Yes, I can see it used internally but I don't see a reason it can be used
> publicly.

I've only just got a couple minutes and I have to run (very busy right now).
There is a bunch of threads and questions here, and I've been meaning to
answer am, but it just don't have the time right now in the next couple of
days to get back to here. And, time spent here means I not dealing with the
ton of isses I need to SharePoint wise.

For that room booking example, that's generally going to be nonpublic
(internal) So, organizations and corporations that have several rooms for
booking will use this web site internal and don't allow the public to book
those rooms.

However I do have plans to add some more event features to that room booking
example. So, you might have a three day technology conference where there's
10 different rooms with each several presentations during the day. In this
case it would most certainly makes sense to have a public facing web site to
allow people to sign up for the seminars and book into those rooms. (and, I
am even looking for payment processing solution for this). Of course this
would allow the organizers know when a room is booked full, or they could
even consider moving it into a larger venue. Printing of each users schedule
and what events etc would be a great use. And the built in email
notification systems in SharePoint are a dead winner for this type of
application.

So, right now the concept and idea behind that room booking application is
for internal organizations and companies that have several board rooms or
simply conference types of rooms to book. However, I can certainly see some
scenarios where I'd like to extend it to a public facing system and I have
plans to do that quite soon in fact, I'm just sorting out the authentication
and logon process for this as we speak now.

In fact I probably would've thrown up a couple links for folks here to try
some my sharepoint stuff in public, but I I'm simply too busy right now to
set this up in a proper fashion for demos, but I will get around to doing
this when some time frees up, but I have too many piles.

However you should keep in mind that there is a growing number of public
facing SharePoint sites.

Ferrari
www.ferrari.com

CASE tractors
http://www1.caseih.com

Viacom
http://www.viacom.com

Here a cool list:
http://www.wssdemo.com/Pages/topwebsites.aspx


So, SharePoint does have the ability to deal with NON Active directory
users. So, most stuff is based on active directory, but Sharepoint also
supports a second method of logon called "forms based authentication". In
effect what it means, is you can build public facing sites, and even design
and build users with a self signup process. You can of course allow
anonymous use of the sharepoint site also. This is a pretty big topic to go
into right now, but suffice to say there is two methods of authentication.
You don't and will not write this user stuff in Access web. Both of these
methods of authentication are pretty much transparent to the rest of the
sharepoint site in terms of how say Access web services will "see" and deal
with the user (and what email is used for when you use the "send mail"
feature of SharePoint for example). And when access web code does things
like GetCurrentWebUser(1), it will work the same for both sets of users. (AD
and FBA).

If you think about the above, it's not common, but I would say extremely
common to have a web site in which you have users sign up and therefore then
be forced to log on or sign in to manage their security. Suffice to say that
sharepoint has support for this. You will however have to setup a self sign
up process with features like passwrod re-set, or even support of those
"captia" (those hard to read grapic things so often seen during signup that
I hate).

I simply have to run, I stop here.....



From: David W. Fenton on 23 Jul 2010 15:34
"Albert D. Kallal" <PleaseNOOOsPAMmkallal(a)msn.com> wrote in
news:Ks12o.14072$hF1.7738(a)newsfe14.iad:

> So, SharePoint does have the ability to deal with NON Active
> directory users. So, most stuff is based on active directory, but
> Sharepoint also supports a second method of logon called "forms
> based authentication". In effect what it means, is you can build
> public facing sites, and even design and build users with a self
> signup process. You can of course allow anonymous use of the
> sharepoint site also. This is a pretty big topic to go into right
> now, but suffice to say there is two methods of authentication.
> You don't and will not write this user stuff in Access web. Both
> of these methods of authentication are pretty much transparent to
> the rest of the sharepoint site in terms of how say Access web
> services will "see" and deal with the user (and what email is used
> for when you use the "send mail" feature of SharePoint for
> example). And when access web code does things like
> GetCurrentWebUser(1), it will work the same for both sets of
> users. (AD and FBA).

So, basically, it sounds like your Access web app would be unchanged
by this, and Sharepoint provides the web wrapper around it for
non-AD user authentication/account setup, etc. But once logged in,
GetCurrentWebUser(1) provides you to check who that non-AD user is.

That seems to cover it!

I'm pretty impressed at how thorough MS has been with implementing
Access Services on Sharepoint. So far, I don't believe I've noticed
anything they've failed to account for.

I may have to entirely change my thinking about how appropriate
Access is on websites.

--
David W. Fenton http://www.dfenton.com/
contact via website only http://www.dfenton.com/DFA/
First  |  Prev  | 
Pages: 1 2
Prev: A2010 question regarding web app
Next: Can't open backend that is in use