If this is a 6 part series then I guess that I'll have to wait 4 more months to get it all.
As a ListX user, I hope that you cover migration from ListX. Clearly is isn't as simple as dropping ListX's XML into OWS's import option, as I tried this several months ago. It
appears as if I may which to re-implement my application from scratch in OWS,
if I can truly share some of the replicated code. For example, could I share the same superset copy of the
query, frm, @, filter definations among all of the different module sets that make up my application?
or would I have to copy the master set into each c
onfiguration and then tweak all of them each time I had to add a new field?
I hope that one of the sessions will deal with searching and also cover checkboxes, which HTML, ListX/OWS, and SQL Server each tend to make a pain in the butt.
Somewhere you might want to address how OWS and its use of Ajax interacts with Google's search enging indexing. I had to completely redesign my ListX implementation, because I needed Google to index some of the content of my database. If the data is display on your browser via an Ajax request rather than from an HTTP
get or
post, then its isn't available for Google to see. As an example, my
Listed_Homes page uses ajax and the content from the bottom module isn't index in Google. As a result I had to create a
Site_Map page which doesn't use Ajax in order to get Google to index the data. Since OWS uses Ajax in additional places, I suspect that this is even more complex today.
It appears that DNCreative has, or soon will have, more information on OWS than R2's has. This shows the value that DNNCreative provides to its users.
Great work Paul and Lee,
/DaveS