Needs review
Project:
Ajaxify Regions
Version:
6.x-1.1
Component:
Miscellaneous
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
18 May 2010 at 23:44 UTC
Updated:
28 May 2010 at 21:49 UTC
Jump to comment: Most recent file
Comments
Comment #1
mikeytown2 commentedWorks for me, let me know what you think.
Comment #2
csevb10 commentedMy concern about this is how it would work for all use cases. For some of the things we've looked at previously, it would work like a charm (aka content that would simply be stale if not served dynamically), but there are a set of use cases where it would serve either wrong or bad content that I'm concerned about (and what the module was really intended to help with):
1. user-specific data (user information, user-specific links, etc)
2. role-specific or inaccessible content (i.e. content that only certain people should see or only that user should have access to, etc)
Let me know if that makes sense. It might make sense to actually come up with some way to make that determination on a per-block basis, so I'll start brainstorming ways to resolve the issue.
Btw, I'll clean up all the whitespace issues so the patches are easier to review. :-P
Comment #3
mikeytown2 commentedI'm using this with the boost module, so I do not have to worry about user/role specific data. In terms of per block configuration we could copy what the domain_blocks module does with hook_form_alter()
Comment #4
mikeytown2 commentedOne more thing that might be good is to have a ajax timeout and if the timeout is reached then default to what's in the noscript tag.