I do not prefer SVN over httpd (as their website seems to recommend). I always go for it straight through ssh. Much simpler and easier to manage, as long as all your users are already ssh users.
So yes, you can easily use ssh identities, or none at all and they have to type in their username/password every time.:)
Alright. Let's look at it a different way. Cookies are assumed private to the "web application", but really only private to the "domain", and with the current broswers/javascript, they aren't even private then.
So is there a way to make cookies truly private to the "web application". So when I actually launch the "web application" "gmail.com" I give that application access to it's private cookie data. If another application tries to access those cookies I would have to grant it access..
How about something like that?
Basically a tighter security model for client-side data. It sounds more like it should be more like Java Webstart. My guess is that Firefox 3.0, with their renewed focus on treating these "web applications" like real the real applications that they are, will have to deal with many of these security/data model questions...
yeah, i know it sounds like an advertisement, but it's my own personal opinion having used both products, and actively using it on protrade.com. I would personally discourage anyone from using hibernate and encourage a look at kodo for any large commercial/production site.
I am definite that Hibernate is not up to the task - at least for our systems. We tried it, we disliked it, and eventually moved away from it. And I am sooo glad we did, because it really would not have handled out load properly!
I strongly, strongly recommend any java developers to look at Kodo (http://www.bea.com/kodo), it is an ORM with both JDO and EJB3 interfaces so it can do both.jdo mappings or ejb3 annotations. It really is enterprise quality, with many features and flexibility all well implemented. The developers behind it are really smart. And yes it's open source!
Anyway, I just owe them a debt of gratitude, our tech would not be the quality it is now if we had gone the hibernate route.. but that's just my opinion.. just go have a look at Kodo.
The best jabber implementation that I have used is Wildfire by Jivesoftware. It was really really easy to install and setup (even with LDAP support), and our company has been using it for months and months. It's really great to have an internal IM server.
It sounds to me like you're trying to do accounts/client management, not journal management. Easily, you might only need to tweek the label printing functionality. You could even look into enhancing their support for "subscription" based services, and you would have everything you wanted.
Slashdot Mirror
Slashdot engine should be used to maintain author and paper karma points, moderation and meta-moderation! Yeah?
I do not prefer SVN over httpd (as their website seems to recommend). I always go for it straight through ssh. Much simpler and easier to manage, as long as all your users are already ssh users.
:)
So yes, you can easily use ssh identities, or none at all and they have to type in their username/password every time.
Alright. Let's look at it a different way. Cookies are assumed private to the "web application", but really only private to the "domain", and with the current broswers/javascript, they aren't even private then.
So is there a way to make cookies truly private to the "web application". So when I actually launch the "web application" "gmail.com" I give that application access to it's private cookie data. If another application tries to access those cookies I would have to grant it access..
How about something like that?
Basically a tighter security model for client-side data. It sounds more like it should be more like Java Webstart. My guess is that Firefox 3.0, with their renewed focus on treating these "web applications" like real the real applications that they are, will have to deal with many of these security/data model questions...
Thoughts?
yeah, i know it sounds like an advertisement, but it's my own personal opinion having used both products, and actively using it on protrade.com. I would personally discourage anyone from using hibernate and encourage a look at kodo for any large commercial/production site.
d o-opensource.html
Yup, the core "kernel" is open and the ejb3 interface is open, but not the JDO interfaces, but they are both implemented by the shared "kernel".. sorry http://dev2dev.bea.com/pub/a/2006/02/interview-ko
I am definite that Hibernate is not up to the task - at least for our systems. We tried it, we disliked it, and eventually moved away from it. And I am sooo glad we did, because it really would not have handled out load properly!
.jdo mappings or ejb3 annotations. It really is enterprise quality, with many features and flexibility all well implemented. The developers behind it are really smart. And yes it's open source!
I strongly, strongly recommend any java developers to look at Kodo (http://www.bea.com/kodo), it is an ORM with both JDO and EJB3 interfaces so it can do both
Anyway, I just owe them a debt of gratitude, our tech would not be the quality it is now if we had gone the hibernate route.. but that's just my opinion.. just go have a look at Kodo.
http://www.jivesoftware.org/wildfire/
The best jabber implementation that I have used is Wildfire by Jivesoftware. It was really really easy to install and setup (even with LDAP support), and our company has been using it for months and months. It's really great to have an internal IM server.
Have a look at Alfresco. It's an up and coming general Content/Document Management system, dual licensed, very flexible.
It sounds to me like you're trying to do accounts/client management, not journal management. Easily, you might only need to tweek the label printing functionality. You could even look into enhancing their support for "subscription" based services, and you would have everything you wanted.
http://www.sql-ledger.org/