[MAGNOLIA-63] page activation requires bidirectional network connection Created: 14/Aug/04  Updated: 14/Sep/04  Resolved: 14/Sep/04

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: 2.0 Final
Fix Version/s: 2.0 Final

Type: Improvement Priority: Minor
Reporter: Boris Kraft Assignee: Sameer Charles
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:

 Description   

In the current implementation page activation requires bidirectional
network connection: the author instance sends a notification to the
public instance, and the public instance connects to the author
instance to download the changed page(s) from the repository. This
is not working in a setup where the author instance is on the
intranet and the public instance is on the web server in the dmz
which is not allowed to connect back to the intranet and therefor
cannot download the changed pages.

Maybe it is possible to modify the implementation to send just one
single POST request to the public instance containing the change
notification and all the changed pages.



 Comments   
Comment by Sameer Charles [ 31/Aug/04 ]

its an open implementation, if someone wanna have push delivery they can implement that. I dont think we should do it for 2.0
activation handler could be configured quite easly so I would leave this on contributers

Comment by Sameer Charles [ 14/Sep/04 ]

reopen it in case..
we wont deliver this, its open so can be programmed

Generated at Mon Feb 12 03:13:44 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.