Re: [Server-devel] Web Caching Issues
I ultimately got wwwoffle working and will make a complete posting on how soon. From a big picture perspective, I installed the Red Hat Enterprise Linux 5 .rpm from the atrpms.net link (wwwoffle-2.8b-2.0.1.el5.i386.rpm). In the wwwoffle.conf file I changed "http-port = 8080" to "http-port = 3128" and in the AllowedConnectHosts section I put "172.18.96.*" which is the IP address range of my access point. Finally I had to set my proxy to 172.18.0.1 port 3128 . I did not have to make any changes to the localhost settings in the wwwoffle.conf file. It would be great to be able to use version 2.9 if you could get a good rpm for it. Thanks for your help, Andy On Mar 24, 2010, at 2:49 PM, Martin Langhoff wrote: > On Mon, Mar 22, 2010 at 9:49 AM, Andra DuPont wrote: >> I took Jerry's second approach and configured wwwoffle to use port 3128. > > Excellent path. I am trying to get a newer version of wwwoffle built > as a good rpm for the XS, and to give you a clear recipe on how to get > this working. I think you are 99% there, just that there may be a kink > or two to sort in your wwwoffle config. > > Apologies about the delay, I have been travelling and without a > machine at hand to develop on. > > cheers, > > > m > -- > martin.langh...@gmail.com > mar...@laptop.org -- School Server Architect > - ask interesting questions > - don't get distracted with shiny stuff - working code first > - http://wiki.laptop.org/go/User:Martinlanghoff ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] [Sugar-devel] scalability in the neighborhood view
On Wed, Mar 24, 2010 at 3:28 AM, Tomeu Vizoso wrote: >> Yep - no prob for me. The GUI side probably needs a bit of extra >> thinking so that it avoids being specific to the backend works (moodle >> in this case)... > > I was thinking that Moodle would put contacts in groups in the server > side and Sugar would just use the standard Telepathy interfaces. Yep. Agreed, same here. What I was thinking about was the UI design... for example, just one very obvious case we have to deal with: it is a good idea to design the UI so that we have a metaphor to edit groups (create, add/remove users). This can work server-less or with XMPP/Moodle backends -- we have to define a "lowest common denominator" and aim to use just that. For the initial implementation we are discussing, I would avoid implementing the client-side editing, and go instead for something easy: just read the groups via Telepathy -> Gabble -> XMPP (which in turn is controlled by Moodle). But if we have a plan for the "full" interaction, we can start implementing the basics. Without looking at the long term UI, maybe we implement something and then... have to change the UI significantly in the "next stage". It's not a big deal... I just think it would be good to have a chat or two to define some of those "lowest common denominators" strategies, and some key "features". An example on the 'feature' side: one of the strongest requests from the field I have is something I don't think we ever thought about -- teachers want to set a mode in Moodle that forces all kids' XOs to only show _this_ group/course/classroom members. Not sure how that'd work but I get that request from several independent deployments. I probably need to think these ideas through, and throw them in the collective pot... if you're interested... cheers, m -- martin.langh...@gmail.com mar...@laptop.org -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] [Sugar-devel] scalability in the neighborhood view
On Tue, Mar 23, 2010 at 17:00, Martin Langhoff wrote: > On Sun, Mar 21, 2010 at 2:59 PM, Eben Eliason wrote: >> maybe we can start with a Moodle-only >> approach and later extend to a generic system that works with or >> without a server. > > Yep - no prob for me. The GUI side probably needs a bit of extra > thinking so that it avoids being specific to the backend works (moodle > in this case)... I was thinking that Moodle would put contacts in groups in the server side and Sugar would just use the standard Telepathy interfaces. In that way, whatever is done in the server side would work for students using Gnome and Empathy, and also other deployments could get creative on the server side without having to fork Sugar. Regards, Tomeu > cheers, > > > > m > -- > martin.langh...@gmail.com > mar...@laptop.org -- School Server Architect > - ask interesting questions > - don't get distracted with shiny stuff - working code first > - http://wiki.laptop.org/go/User:Martinlanghoff > ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
