You don't need any "page" actually (though you might *want* pages),
and your challenge doesn't talk about "bookmarkability" (well, because
you say it should use HTTP POST, I believe you're "modifying a
resource's state" and therefore the URL for, e.g., "page 2" is the
same whichever the value you entered in "page 1"; ...and now that I
looked at your swf1's sample, it seems this really is the case: the
URL doesn't change between "pages").
This leads me to say that your "challenge" is completely "not web-
style", it reminds me of JSF (don't ask me what I think of it, I can
become angry quite quickly).
Instead of focusing on "page flows" (why are there so many frameworks
doing such a shitty thing?), (learn REST if needed and then:) focus on
resources and their states, moving application state to the client
(and therefore building a stateless server, where you don't even need
"sessions"), etc.