Vitor Domingos wrote:
>Great ideia. I've already told you that I'm willing to support the
>Portuguese language, thru zion.paradigma.pt.
Fantastic, thanks Vitor.
>I'll add more questions to your email:
>- Who'll mantain the pootle versions?
>- Will this person need login into the local machines?
>- The sync process with the various servers will be done in a secure
>manner? How? SSL?
>- What are the plans for fault tolerance servers? Will they be sync'ed
>thru nights and between them?
Aha, these are all the questions to answer.
So far I haven't thought this through completely, so any input is valued.
I can see this working in three steps
1) Shared Login
I think we need a way to support shared login, perhaps we could use an
existing mechanism like OpenID (http://www.danga.com/openid/) so that
people only need to register on one site. Then other sites can enable
shared login from whichever sites they prefer.
Rights would be managed by the local server administrator, since we are
splitting things up by project anyway this would be fine.
2) Project Redirection
Say somebody logins into pootle.wordforge.org and then wants to work on
a Portuguese project. The link redirects them to zion.paradigma.pt and
automatically logs them in there.
This should be fairly simple
3) Transparent redirection
This could involve proxying through the server you are using so that
your queries go to another server but you are not aware of it.
This would need some more infrastructure - basically the files are
synchronised between sites.
The easiest level would be doing a master that is read-write and then
only allowing read-only access when in failover mode (but this would
still be useful).
It would be more complex to handle changes being made on more than one
In terms of managing different Pootle versions, the less the integration
the easier it is - so 1, 2, 3 above should be fairly simple as long as
the different versions support the same login system
>David Fraser wrote on 06/06/2005 04:25 PM:
>>I've been thinking about ways to handle much load with Pootle and also
>>the need for fast servers, so this is an idea to bounce around...
>>It would be nice to be able to delegate certain applications / languages
>>within Pootle to a different server, but to still see them all from the
>>same main interface.
>>So for example, you could say that all Greek applications are handled by
>>a certain server, or all OpenOffice.org translations by a certain server.
>>The main issue would probably be about synchronizing login details -
>>once that is done, you could just pass login details from one server to
>>another, and the rest should just work. Since most of the Pootle code
>>operates below the language/project level, not much other co-operation
>>would be required.
>>We could also mirror translations between sites, and designate one as
>>the site that handles changes etc...
>>What do folks think? Would this be a useful thing?
>>This SF.Net email is sponsored by: NEC IT Guy Games. How far can you
>>a projector? How fast can you ride your desk chair down the office luge
>>If you want to score the big prize, get to know the little guy. Play to
>>win an NEC 61" plasma display: http://www.necitguy.com/?r=20
>>Translate-pootle mailing list