Promised I would get back on this, but due to a change in our project's requirements we didn't end up using the mongodb sessionstorage either way, so I didn't find any time to fully investigate this. All I did find out is that under certain specific circumstances a structure which was generated in a session stored component would be case sensitive if it came from mongodb and not case sensitive if the session storage was normal. As I said before, I couldn't pin down what the cause of this was, nor could I replicate it in a very simple test case, but just wanted to let you know that something is definitely buggy about the mongodb sessionstorage. Still love the feature though and we still might use it for a new project some day in the future and if we hit the same bug again we will get back on that. Greetings, David Mulder
On Thursday, March 21, 2013 12:52:13 PM UTC+1, Alan Williamson wrote: > > > On 21/03/2013 05:17, David Mulder wrote: > > Hi, > > > > Last week I attempted moving the sessionstorage of one of our > > applications to mongodb and encountered a few issues which I would > > like to confirm with you guys: > > > > First of all, when using the "this.sessionStorage" functionality of > > the application.cfc, did I correctly observe that this A) uses > > openbd's own session handling (and not j2ee sessions) > > You can specify which session manager you wish to use. If you wish to > use mongo as the back end then you will use the OpenBD one. > > > and B) that it doesn't work with components in the session? > > It works beautifully with CFC's -- we use that all the time. > > > > Lastly: The connection string for mongodb looks like > > "mongo://user1@pass1:10.0.0.1:27017" which seems odd, because the > > 'official' format for this is scheme://username:password@domain:port > > (the @ and : switched). Was this a conscious choice or is this some > > weird oddity? > > I think that is an error in the documentation. I will confirm. We > don't run our Mongo's behind username/passwords. We instead use the > network/firewall to secure our boxes down, which has been the > recommended path for installing Mongo. Only recently in 2.4 have they > actually seriously addressed security. > > > -- -- online documentation: http://openbd.org/manual/ http://groups.google.com/group/openbd?hl=en --- You received this message because you are subscribed to the Google Groups "Open BlueDragon" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
