| Angus Logan [MVP] 2004-10-02, 9:00 pm |
| Hi Spence,
I am specifically talking about intranets that use CMS+SPS+WSS.
One solution that I am looking at is:
CMS - Primary web interface (displays info from SPS & links to SPS/WSS
sites)
SPS - searching & profiles etc.
WSS - lists that need to be bubbled up to CMS & documents that need to be
collaborated on then possibly displayed in CMS
Cheers
--
________________________________________
Angus Logan (MCAD/MCDBA/MCP/MVP for MCMS)
Product Specialist
Microsoft Application Solutions
Data#3 Limited
E angus_logan@data3.com.au
BLOG www.anguslogan.com
________________________________________
"Spencer Harbar [MVP]" <spence@harbar.net> wrote in message
news:OreRPG8pEHA.800@TK2MSFTNGP14.phx.gbl...
> My thoughts are that such a decision could be largely based on the
intended
> audience for the solution.
> As a massive generalisation, due to authentication mechanisms (oh, and
> licencing  ) SPS is primarily an intranet facing system, whereas CMS is
an
> Internet facing one.
>
> If the solution is as you say content focused then I'd definately go with
> CMS as the entry point.
> There are obviously a few downsides, but this is the approach used by
MSIB -
> which I'd say is the best reference in this area. Whilst the key
> functionality is CS, CMS is used as the entry point.
> MSIB also has a bunch of SPS related points now.
>
> You can generally solve the no personalisation problem by using MSIB, or
> bespoke code.
> Just from a content perf/scale perspective, CMS is massively more
scaleble.
>
> --
> hth
> Spence
> www.mcmsfaq.com
>
>
> "Angus Logan [MVP]" <angus_logan@data3.com.au> wrote in message
> news:OOnXKhtpEHA.3428@TK2MSFTNGP11.phx.gbl...
CMS.[vbcol=seagreen]
from[vbcol=seagreen]
SPS///[vbcol=seagreen]
collaboration[vbcol=seagreen]
with[vbcol=seagreen]
>
>
|