Pin-pon! Yes, Memory Serves is a CherryPy application. Beautiful framework, simple yet powerful.

My online word count tool was my first attempt at a “production” CherryPy app — it was kind of a proof-of-concept project for using CherryPy with Memory Serves. It turned out to have everything I needed, and has allowed me to make very quick progress with this project.

Having rules against running a server would make it very hard to use translation memory collaboratively at work. The other local solution I’m aware of would be DCOM, but that has a lot of security issues, and not even Microsoft seem to be pushing it any more.

I wonder what they would think about using an offsite server over SSL? Or running their own Internet facing server over SSL (if the local-ness is the problem)?

I’ve been told quite a few times by the Powers That Be that I’m not allowed to run a server on our network under any circumstances, so I wonder what they will think of Memory Serves. I suppose I’ll find out soon enough.

Does this release mean that Felix has acquired a taste for CherryPy, by any chance?

Thanks a lot for the feedback. Yes, I can see a use case there for restricted access. The easy way would be to simply password protect certain actions (like deleting memories). The harder way (but in the end probably the best) would be to add a login system. I’ll plan on having some sort of access restriction by the official 1.0 release later this month. (I’ve just released version 0.1, and will be blogging it in a moment.)

Right now the server operates over HTTP, which prevents truly secure password protection. I’m eventually going to put a free public memory server on the Felix website, which will use SSL; at that time I plan to update Memory Serves to enable an SSL option.

In our office, we have some translators who are employees and some who are temps. It might be convenient for us to be able to prevent the temps from deleting memories, but it certainly isn’t as high a priority as making the TMs available for everyone to share.