Am 22.04.2012 20:00, schrieb Michael Heydekamp:
session != browser window
Ok. There is a menu item "Neue Sitzung" (= new session), that's why I thought it may have to do with it.
depends on the point of view and implementation in MSIE6 it was really a new session after MSIE6 i switched completly to linux
in all other browsers if you open a new window it is simply a new window but having all session cookie
in the world of browser/webservr/web-application a session is defined by a session cookie and some storage on the server (in case of PHp normally the session-file) with the depending server side data identified by the session ID which is usually sent via cookie or in unsecure applications even via GET (PHPSESSID param)
And because: As a matter of fact, I can currently load Roundcube in a new window/session/instance of IE (be it InPrivate or not), but not in a new tab of the same (first) IE window/session/instance.
yes because as said MSIE tends to trhow away existing session cookies if you start a new window
session is at least a id sent via cookie switching to "private mode" will stp sending this cookie
And that has exactly which consequences?
that if a script called with a ession-cookie doing start_session() in php is locking the session-file on disk until the script has finished or sessin_write_close()
this means as example if you are seinding a large file with fpassthru() and did session_start() and not session_write_close() before starting send data EACH connection from the same cient to a script which calls session_start() has to wait until the previous one has finished his operations (the download in example)
you can notice this also in framesets all using php-sripts with start-session() - if you are doing session_write_close() as soon as possible from the point where you are sure that you do not need write any session variable all frames will appear much faster
Surprisingly, InPrivate mode currently seems to be the only mode in which I can run Roundcube without these kind of problems at all. At least I haven't seen any such yet, even not after sending messages.
maybe it does not braindead switch the user-agent
as far as i understood the html-editor for message-coompose seems to trigger a user-agent change in some cases - if this is true the component has a major bug
And this arises the question: What's this session and cookie thingy all about, if RC is running perfectly without them (except that the pane sizes are not saved)?
it does NOT work without them
without them you would have to enter your userdata for each request - you can not write any application with login without sessions
the private mode is also accepting session cookies but it seems not to change stupidity his user agent
as far as i understand someone has to patch the html-editor shipped with roundcube and the problem may go away!
Well, IE "years ago" has to be contemplated differently to IE8/9 (which you will know a lot better than me).
things got better but MSIE is still bullshit
Anyway, a sophisticated application such as Roundcube is for sure not meant to be one of those "best viewed with browser xyz".
true
What's really and still puzzling me, is that I haven't seen any of those problems with Squirrel for years (also under IE). And I really and finally would like to get rid of it.
it scares me too because we are about replacing horde currently