<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On 30 Jul 2008, at 02:27, John Beppu wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr"><br><br><div class="gmail_quote">On Tue, Jul 29, 2008 at 5:21 AM, Daniel McBrearty <span dir="ltr"><<a href="mailto:danielmcbrearty@gmail.com">danielmcbrearty@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> my 0.05 (possibly a bit OT) :</blockquote><div><br>Off-topic or not, I think these are interesting and valid questions.<br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> I looked previously at a few ways of adding forums etc to the site<br> using 3rd party code, indeed there are many possibilites (some perl,<br> some not)<br> <br> The thing that was always a sticker for me was getting some kind of<br> logical integration, ie:<br> <br> 1. letting users keep existing member and login creds</blockquote><div><br>Now that composition and embedding of web apps is becoming a reality, we have to start anticipating needs like this. For example, the documentation for an app that's built to be embedded could state that:<br> <ul><li>It expects a user object to be in its session's "u" key.</li><li>The app will expect to be able to call the ->name method on this user object. (Some apps may want more... others less... this is just a hypothetical example.)<br> </li><li>If that key is undef, the app will assume the current session is not in a "logged in" state.<br></li></ul> I think being up-front about login policy would be enough to share users across multiple web apps joined together as one cohesive unit.</div></div></div></blockquote><div><br class="webkit-block-placeholder"></div><div><br class="webkit-block-placeholder"></div><div>I dont. Lets take the example of embedding a forum. It will most likely store its data in a DB of its own design. It will also quite likely have its own user table, and have FKs referencing that table.... see the problem? There's more to sharing users than just logging. </div><div><br class="webkit-block-placeholder"></div><div>I can't really see any way around that other than on a case-by-case basis sadly. Someone please feel free to correct me.</div><div><br class="webkit-block-placeholder"></div><div>-ash</div></div></body></html>