not supported VS not possible

Topics: Web Client Software Factory
Jan 22, 2007 at 8:16 PM
Below is a quotation from the Page Flow Application Bloc documentation. For the scenarios mentioned as non supported (or non-goals): does that mean "other solutions can be used instead" or "features are impossible to use" with the Page Flow Application Bloc?

TIA

From Page Flow Application Bloc documentation

"The following are the non-goals for this application block:
Works well within different application domains. The application block targets ASP.NET applications. It is not a goal to support console applications, Windows Forms, or Avalon forms-based applications.
Works with existing User Interface Process (UIP) Application Block applications. You must modify UIP applications to use the application block. For migration guidance, see Migrating from the UIP Application Block and Page Flow with Shopping Cart."

"Scenarios Not in Scope
This version of the Page Flow Application Block does not include support for the following scenarios:
Progress indicators (also known as "bread crumbs")
Pop-up windows
Shared transitions between different page flows
Query string management
Multiple sessions by the same user (for example, the user has a Web client application open in two browser instances at the same time)
Multiple users running applications that use the application block on the same computer (the default page flow correlation token provider, CookiePageFlowCorrelationTokenProvider, does not support this)"
Developer
Jan 23, 2007 at 2:11 AM
Hi,
The non-goals of the block are features not covered by the application block out of the box. This means that if you want to have those features, you will have to extend or modify the block (depending on the complexity of the feature).

Did I answer your question?

Cheers,
Mariano Szklanny
http://staff.southworks.net/mariano
Jan 23, 2007 at 1:29 PM
Thanks Mariano!

What about the "Scenarios Not in Scope" like
- bread crumbs,
- pop-up windows,
- query string management, etc?

Those features are involved in almost every web application. Are custom solutions possible with the Page Flow Application Block and WCSF in general? What would be the effort required to integrate such solutions with the Page Flow Application Block and WCSF?
Coordinator
Jan 23, 2007 at 7:50 PM
Are custom solutions possible with the Page Flow Application Block and WCSF in general?
Yes, they should be. There is nothing in the architecture that precludes any of these features. Most were cut from the first release due to time contraints or other factors.

What would be the effort required to integrate such solutions with the Page Flow Application Block and WCSF?
It would depend on the feature you wanted to add, the solution, if the solution already existed, and a number of other factors. Making an estimate with this many unknowns is not something I would be willing to do for my team, let alone yours. :-)
However, I don't see any of the features as terribly complex to add. They should fit into the architecture pretty well. The pop-up might be a little tricky based on how other things are managed in the PageFlow block (abandonable vs. non-abandonable PageFlows for example), but if you limit pop-ups to non-abandonable pageflows or include the pop-up pages in the PageFlow, it should be relatively simple.
Jan 23, 2007 at 8:12 PM
Each application block is designed to be both used out of the box and extended. In the case of the three "Scenarios Not in Scope" you listed, these are things that just didn't make it into this release (as an fyi, we ended up doing a lot of work on performance near the end, which was very beneficial, but resulted in some features being cut.)

Each of these would require you to write some code, and most likely modify the applicaiton block, but should be possible.

Also, please consider voting for things (in the Issue Tracker) that you want to see us incorporate into the next release.

Thanks,
Tim