tag:blogger.com,1999:blog-4126985520350746834.post1544600429019839663..comments2010-07-31T19:48:10.101+01:00Chris O'Brienhttp://www.blogger.com/profile/10022906552670607366noreply@blogger.comBlogger8125tag:blogger.com,1999:blog-4126985520350746834.post-52834161065094512452009-01-19T07:58:00.000Z2009-01-19T07:58:00.000ZHi Raj,<BR/><BR/>Sorry, I no longer have access to these documents. <BR/><BR/>All the best with your project..<BR/><BR/>Chris.Chris O'Brienhttp://www.blogger.com/profile/10022906552670607366noreply@blogger.comtag:blogger.com,1999:blog-4126985520350746834.post-35306648211180972032009-01-17T01:56:00.000Z2009-01-17T01:56:00.000ZChris,<BR/><BR/>Can you share the project plan/task list that was used for this project? We're starting to build a WCM site with Endeca integration, so the project plan will be extremely useful.<BR/><BR/>Thanks!<BR/>-RajAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-4126985520350746834.post-62934675175472382892008-08-25T11:29:00.000+01:002008-08-25T11:29:00.000+01:00Hey Saul,<BR/><BR/>We didn't use AJAX (no specific need to), but our interface developer did use the <A HREF="http://jquery.com/" REL="nofollow">jQuery</A> JavaScript library, and I think this is in common use at LBi. <BR/><BR/>Sure, I'd be up for a drink sometime :-)<BR/><BR/>Take care,<BR/><BR/>Chris.Chris O'Brienhttp://www.blogger.com/profile/10022906552670607366noreply@blogger.comtag:blogger.com,1999:blog-4126985520350746834.post-76066768239500939192008-08-21T00:04:00.000+01:002008-08-21T00:04:00.000+01:00Interested to know what javascript libraries you chose to use on your project.<BR/><BR/>LBi - wow I work just up the road in Fashion street - should get together for a drink.<BR/><BR/>SaulSaul Tombukhttp://www.blogger.com/profile/18162962442002925471noreply@blogger.comtag:blogger.com,1999:blog-4126985520350746834.post-44839020101965009732008-08-20T18:36:00.000+01:002008-08-20T18:36:00.000+01:00slp,<BR/><BR/>Maybe I can answer here - you kind of hit upon some of the complex issues in a way. In actual fact, we authenticated users against a SharePoint list with a custom provider, but this was forced on us (wouldn't have been my choice under all the circumstances, and the plan is to change this fairly soon). The reason this was forced on us is actually to support the single sign-on - the sister site (also on MOSS) already existed and authenticated users in this way. For us to provide single sign-on with the same username and password, we effectively need to use the same authentication provider. In terms of the single sign-on itself, this is actually handled by .Net cookie sharing, and means that users can pass authenticate against one site and pass between each without being reprompted to login. All good.<BR/><BR/>One of the reasons we're looking to change the authentication model is because it kind of works for 2 sites, but in the future we might have 20. In this scenario, we'll have many more users and certain issues arise (scale, performance, slightly unorthodox design of authentication store being tied to one site) which mean SQL authentication is a better choice IMHO. In addition, we currently require some fairly intelligent code for creating users which deals with creating the user, creating a default profile, assigning to correct security groups in each site, and rationalizing the way we deal with authentication and profiles should hopefully simplify this picture somewhat.<BR/><BR/>In short, the kind of issues which can crop up with multiple sites, many users, and heavy use of user profiles. But that's the interesting stuff right? ;-)<BR/><BR/>HTH,<BR/><BR/>Chris.<BR/><BR/>P.S. If you have further queries let me know and I'll try to give more details.Chris O'Brienhttp://www.blogger.com/profile/10022906552670607366noreply@blogger.comtag:blogger.com,1999:blog-4126985520350746834.post-13212858451569324952008-08-20T14:21:00.000+01:002008-08-20T14:21:00.000+01:00I'm currently working on a project that will be maintained by authors around the country, and this is the first I've seen of use MOSS in an envirornment for users who are not in one centralized area. <BR/>What method of authentication did you use for this? Was it just the forms-based sqlmembership store, or did you guys create your own memberhip? I'd love to know more about how you handled the single sign-on with a sister site (not MOSS-based, I would assume). Any chance you'll be writing a blog on this?slpnoreply@blogger.comtag:blogger.com,1999:blog-4126985520350746834.post-18859653043469667642008-08-14T13:06:00.000+01:002008-08-14T13:06:00.000+01:00Rohan,<BR/><BR/>It varied slightly over the course of the project, but in total we used 5-7 guys - myself and 4 other SharePoint devs, an Endeca guy and an interface developer (front-end guy).<BR/><BR/>You'll have to believe me when I say we were going at full tilt though :-)<BR/><BR/>Cheers,<BR/><BR/>Chris.Chris O'Brienhttp://www.blogger.com/profile/10022906552670607366noreply@blogger.comtag:blogger.com,1999:blog-4126985520350746834.post-13969288237177121792008-08-14T03:30:00.000+01:002008-08-14T03:30:00.000+01:00this is insane . I like all the Ui stuff. How many people in 7-8 weeks ?Rohanhttp://www.blogger.com/profile/02999243506518689180noreply@blogger.com