Sure, get rid of the SeamRedirectFilter. But then you lose *really* nice stuff like propagation of the temporary conversation state across a redirect.
It is kind of annoying since the id increases in each page rendered, making the whole site look quite unprofessional.
Why would a parameter in the url make the site look unproffesional? Normal users don't look at the parameter list... And developers will appreciate that you are using advanced technology to make sure that your site doesn't produce the bug that so much other sites trouble. Else they are just stupid ;)
The cid (what conversationId has been shortened to in cvs) shouldn't be necessary after a conversation has ended. It does have a tendency to hang around however, at least as I've observed in the seam scaffold application. I wonder if cid could be stuck in a cookie instead?
You want nasty looking, try surfing around a Broadvision-powered site.
It "hangs around" because temp conversations propagate across redirects.
No, you cannot use a cookie, because that is not scoped to a browser window.