Originally Posted by
baliktad
There is a huge disconnect in what users are asking for (keep me logged in) and what EF Voice is saying can't be done.
Of course the logical fallacy is when the jump occurs from "keep me logged in" to "keep an active session on the server," which no user has asked for. Plenty of sites much larger and more complex than EF have figured out how to do it. It's very difficult to believe this request is technically impossible. It seems much more likely that EF either completely misunderstands the request, deems it too expensive to justify, or is simply unwilling to adjust its service to accommodate its paying users.
You're misunderstanding my response. "keep me logged in" vs "keep an active session on the server" are not two different things, they are technically linked and changing one requires us to change the other to ensure continuity and to not introduce user confusion when, say for example, a Refine Query link is clicked and a blank search form is shown instead because the users session information has timed out, or they are sent back to the page you see after login, etc.
If you require a more technical response, feel free to email us at
[email protected] and we can talk about this off-line since you can't really know what can/can't be done or how without knowing how our system works. Nothing is "impossible", everything is just a trade-off or a matter of priority, as is the norm for a small business.
However, don't think for a moment that we don't accommodate requests for tweaks and new features when possible, we do it all the time, and it's a big factor in our product road map. Flight Alerts, Seat Alerts, the Mobile site, numerous tweaks to the UI - all user requests. The latest user request we accommodated is showing both the equipment code we receive from the airline as well as our description of it for Seat Map responses. This way you know which equipment sub-type an aircraft is for airlines that make up their own equipment codes (like BA). We released that two days ago.
Please send all feature requests/suggestions to
[email protected] so we can have them saved for proper evaluation. Thank you.