From: Wayne McAlpine
As I understand it, Joe, FRCA searches its cache for a matching URL. My
guess is that it won't handle a POST.
That's an important issue for application design!
In general your server side doesn't really care about POST vs. GET and I
have always tended towards POST simply because I don't like people fiddling
with the URL.
However, that's because a lot of my work is with traditional procedural
applications where screen order is important, and so I can get away with
GET is required for bookmarking, and now it looks as though it's necessary
for FRCA as well. This is definitely not any sort of knock on FRCA; the
sort of applications FRCA is well suited for are usually the kind where
bookmarking makes sense. Again your application is a great example. I
could definitely see someone bookmarking several races and bouncing between
them, whereas I don't support bookmarking the middle of an order in a
traditional OLTP environment.