Albert Lash wrote:
> I made a release of 3.1 at SF today.
I noticed that, thanks. I was actually thinking of doing that today when
I got to work.
> An additional thought I had was to
> consider having "sites", so that the same PSA source could get used for
> multiple sites. That would be smart I think. Sort of like a profile feature
> for site structures. What do you think?
I have thought about that, but haven't gotten around to planning it out
yet. Part of the problem was that you'd have to pass the site's domain
so you knew where the request was comming from. However, I didn't give
it enoughthough to come up with a transparent, clever way of doing that
yet. You can't rely on the HTTP_REFERER for it, and if it is at a
central location, you can't rely on HTTP_HOST either... REQUEST_URI
doesn't provide the domain, and SERVER_NAME wouldn't be any help either.
Once I figured all that out, I stopped thinking of it because it
wasn't necessary for me at the time.
> I guess it wouldn't make much of a functional difference, but would make
> managing the system much easier.
The biggest thing is not to change the API, or at least keep it
backward-compatible. There would likely be a bit of work to do on the
hasRights method since that would be the only one that would really need
modifying.
The other thing to keep in mind is if we were to use XML site mapping,
then there would have to be a way of managing that within the structure
as well.
It's all pretty complicated, but give it some thought and let me know
what you come up with... I am still pretty swamped, but hope to lighten
up a litle here in the next few weeks.
|
