Hi all,
Since yesterday, I've joined Goran as a mantainer of the DynamicBindings, KomServices and KomHttpServer packages.
We've also moved the KomHttpServer packages from Goran's own repository to Samir Saidani's KomHttpServer repository on SqueakSource (see http://www.squeaksource.com/KomHttpServer.html ). In this new repo you'll find new versions of DynamicBindings, KomServices and KomHttpServer that integrate various fixes and modifications by me, Goran, Philippe, Ron and others.
I've already released a new version of KomServices on SqueakMap. A new version of DynamicBindings will follow as soon as Goran adds me to that package (he's at OOPSLA in Vancouver right now). A new version of KomHttpServer will land in SqueakMap after some more testing of the new package.
bugs.squeak.org has a new KomHttpServer category in the Squeak packages project. All bugs posted to this category will be assigned to me.
In the next days, I'll come up with a roadmap for future developments of the package. Meanwhile, I'll start looking at the already existing bugs.
Ciao,
Giovanni
Le 24/10/07, Giovanni Corriga giovanni@corriga.net écrivait :
Snipp....
(he's at OOPSLA in Vancouver right now).
Hi Giovanni, humm....in Montreal not Vancouver there is around 4800 kilometers between the two....
:)
Ciao
Ciao,
Giovanni
On 10/24/07, Giovanni Corriga giovanni@corriga.net wrote:
In the next days, I'll come up with a roadmap for future developments of the package. Meanwhile, I'll start looking at the already existing bugs.
That's very cool. My proposed would be speed, responsiveness and HTTPS. For example, if someone is running a web server it's a fair chance that's the most important application in the image to be responsive, so scheduling should reflect that (if it doesn't already).
I like Commanche because it feels like it has the capabilities of Apache [1] but without that awful configuration.
[1] Apache has more modules of course, but you could do the same thing with Commanche I think.
On Wed, 2007-10-24 at 12:34 +0200, Giovanni Corriga wrote:
Hi all,
Since yesterday, I've joined Goran as a mantainer of the DynamicBindings, KomServices and KomHttpServer packages.
We've also moved the KomHttpServer packages from Goran's own repository to Samir Saidani's KomHttpServer repository on SqueakSource (see http://www.squeaksource.com/KomHttpServer.html ). In this new repo you'll find new versions of DynamicBindings, KomServices and KomHttpServer that integrate various fixes and modifications by me, Goran, Philippe, Ron and others.
I've already released a new version of KomServices on SqueakMap. A new version of DynamicBindings will follow as soon as Goran adds me to that package (he's at OOPSLA in Vancouver right now). A new version of KomHttpServer will land in SqueakMap after some more testing of the new package.
bugs.squeak.org has a new KomHttpServer category in the Squeak packages project. All bugs posted to this category will be assigned to me.
In the next days, I'll come up with a roadmap for future developments of the package. Meanwhile, I'll start looking at the already existing bugs.
This is very good news. Do you know right now how encodings will be handled? Will there be support for 3.8 and 3.9?
If it isn't on your todo list already please put handling of multipart fields onto it. At the moment WAKomEncoded39 converts every response to utf8 but it doesn't do the reverse on processing multipart fields. Dealing with with html forms with and without uploads gives you different encodings. I'll attach a file which fixed this for me but I think there a other solutions which are way better than mine.
regards,
Norbert
Il giorno ven, 26/10/2007 alle 09.41 +0200, Norbert Hartl ha scritto:
On Wed, 2007-10-24 at 12:34 +0200, Giovanni Corriga wrote:
Hi all,
Since yesterday, I've joined Goran as a mantainer of the DynamicBindings, KomServices and KomHttpServer packages.
We've also moved the KomHttpServer packages from Goran's own repository to Samir Saidani's KomHttpServer repository on SqueakSource (see http://www.squeaksource.com/KomHttpServer.html ). In this new repo you'll find new versions of DynamicBindings, KomServices and KomHttpServer that integrate various fixes and modifications by me, Goran, Philippe, Ron and others.
I've already released a new version of KomServices on SqueakMap. A new version of DynamicBindings will follow as soon as Goran adds me to that package (he's at OOPSLA in Vancouver right now). A new version of KomHttpServer will land in SqueakMap after some more testing of the new package.
bugs.squeak.org has a new KomHttpServer category in the Squeak packages project. All bugs posted to this category will be assigned to me.
In the next days, I'll come up with a roadmap for future developments of the package. Meanwhile, I'll start looking at the already existing bugs.
This is very good news. Do you know right now how encodings will be handled? Will there be support for 3.8 and 3.9?
I will use 3.10 for development and test on 3.8, 3.8.1 and 3.9 . I will support earlier versions on a request basis. As for encodings, the latest stable version includes a patch provided by Philippe that makes encoding handling in Seaside easier. I am also considering exploring the possibility of moving part of Seaside's encoding handling logic to Kom.
If it isn't on your todo list already please put handling of multipart fields onto it. At the moment WAKomEncoded39 converts every response to utf8 but it doesn't do the reverse on processing multipart fields. Dealing with with html forms with and without uploads gives you different encodings. I'll attach a file which fixed this for me but I think there a other solutions which are way better than mine.
According to Philippe Marschall, the new KomHttpServer 7.0.5 that I've just published on Squeak Map makes WAKomEncoded39 unnecessary. Can you reproduce the same bug using WAKomEncoded, too? In case, would you mind posting the bug report and the suggested fix on Mantis?
Giovanni
According to Philippe Marschall, the new KomHttpServer 7.0.5 that I've just published on Squeak Map makes WAKomEncoded39 unnecessary. Can you reproduce the same bug using WAKomEncoded, too? In case, would you mind posting the bug report and the suggested fix on Mantis?
Everything is fine with WAKomEncoded. The processing of fields is done regardless of get and post requests. Very good!
thanks to all,
Norbert
2007/10/26, Norbert Hartl norbert@hartl.name:
On Wed, 2007-10-24 at 12:34 +0200, Giovanni Corriga wrote:
Hi all,
Since yesterday, I've joined Goran as a mantainer of the DynamicBindings, KomServices and KomHttpServer packages.
We've also moved the KomHttpServer packages from Goran's own repository to Samir Saidani's KomHttpServer repository on SqueakSource (see http://www.squeaksource.com/KomHttpServer.html ). In this new repo you'll find new versions of DynamicBindings, KomServices and KomHttpServer that integrate various fixes and modifications by me, Goran, Philippe, Ron and others.
I've already released a new version of KomServices on SqueakMap. A new version of DynamicBindings will follow as soon as Goran adds me to that package (he's at OOPSLA in Vancouver right now). A new version of KomHttpServer will land in SqueakMap after some more testing of the new package.
bugs.squeak.org has a new KomHttpServer category in the Squeak packages project. All bugs posted to this category will be assigned to me.
In the next days, I'll come up with a roadmap for future developments of the package. Meanwhile, I'll start looking at the already existing bugs.
This is very good news. Do you know right now how encodings will be handled? Will there be support for 3.8 and 3.9?
If it isn't on your todo list already please put handling of multipart fields onto it. At the moment WAKomEncoded39 converts every response to utf8 but it doesn't do the reverse on processing multipart fields.
Yes it does. It does not for file uploads. There isn't even way of knowing whether an uploaded file is a textfile or not. There is no way of knowing what encoding it has because the operating system of the client doesn't even know.
Cheers Philippe
Dealing with with html forms with and without uploads gives you different encodings. I'll attach a file which fixed this for me but I think there a other solutions which are way better than mine.
regards,
Norbert
On Fri, 2007-10-26 at 10:48 +0200, Philippe Marschall wrote:
2007/10/26, Norbert Hartl norbert@hartl.name:
On Wed, 2007-10-24 at 12:34 +0200, Giovanni Corriga wrote:
Hi all,
Since yesterday, I've joined Goran as a mantainer of the DynamicBindings, KomServices and KomHttpServer packages.
We've also moved the KomHttpServer packages from Goran's own repository to Samir Saidani's KomHttpServer repository on SqueakSource (see http://www.squeaksource.com/KomHttpServer.html ). In this new repo you'll find new versions of DynamicBindings, KomServices and KomHttpServer that integrate various fixes and modifications by me, Goran, Philippe, Ron and others.
I've already released a new version of KomServices on SqueakMap. A new version of DynamicBindings will follow as soon as Goran adds me to that package (he's at OOPSLA in Vancouver right now). A new version of KomHttpServer will land in SqueakMap after some more testing of the new package.
bugs.squeak.org has a new KomHttpServer category in the Squeak packages project. All bugs posted to this category will be assigned to me.
In the next days, I'll come up with a roadmap for future developments of the package. Meanwhile, I'll start looking at the already existing bugs.
This is very good news. Do you know right now how encodings will be handled? Will there be support for 3.8 and 3.9?
If it isn't on your todo list already please put handling of multipart fields onto it. At the moment WAKomEncoded39 converts every response to utf8 but it doesn't do the reverse on processing multipart fields.
Yes it does. It does not for file uploads. There isn't even way of knowing whether an uploaded file is a textfile or not. There is no way of knowing what encoding it has because the operating system of the client doesn't even know.
I didn't mean "converting the upload". I meant conversion of the fields that come along with the upload (or fields that come via post request). The issue is solved. See my other posting.
thanks,
Norbert
Seems after Intel Microsoft too is joining the bandwagon of OLPC after ridiculing it as a toy initially.
http://www.smh.com.au/news/technology/microsoft-sees-window-of-opportunity-i n-lowcost-laptop/2007/10/26/1192941297938.html
Hi,
On 10/26/07, Tansel tansel@squeakonline.com wrote:
Seems after Intel Microsoft too is joining the bandwagon of OLPC after ridiculing it as a toy initially.
were they joining the bandwagon, they would abstain from porting Windows XP to the XO. It's a hardware/software system of a piece, with an actual purpose, not just another laptop.
(In other words: will they also port Sugar to XP?)
Best,
Michael
Sorry with my comment, but nothing good, nothing to the commonweal may be expected from MS.
Cheers.
2007/10/26, Michael Haupt mhaupt@gmail.com:
Hi,
On 10/26/07, Tansel tansel@squeakonline.com wrote:
Seems after Intel Microsoft too is joining the bandwagon of OLPC after ridiculing it as a toy initially.
were they joining the bandwagon, they would abstain from porting Windows XP to the XO. It's a hardware/software system of a piece, with an actual purpose, not just another laptop.
(In other words: will they also port Sugar to XP?)
Best,
Michael
Showing once again the complete cluelessness of Microsoft.
Gary
----- Original Message ----- From: "Tansel" tansel@squeakonline.com To: "'The general-purpose Squeak developers list'" squeak-dev@lists.squeakfoundation.org Sent: Friday, October 26, 2007 6:11 AM Subject: Interesting news: Microsoft working on running XP on OLPC XO
Seems after Intel Microsoft too is joining the bandwagon of OLPC after ridiculing it as a toy initially.
http://www.smh.com.au/news/technology/microsoft-sees-window-of-opportunity-i
n-lowcost-laptop/2007/10/26/1192941297938.html
gafisher wrote:
Showing once again the complete cluelessness of Microsoft.
Well, what do you think a third world politician (although first world ones are no different really) with no clue about technology will do given the following choices to blow 100 million $ on the OLPC:
risk it on a buggy, delayed, unproven system software or go with world wide established Windows?
Just to be sure nobody gets this wrong. This is not my opinion, I'm just stating what I think might happen...
Michael
Depends if those politicians have invested own money in anti-virus market or not...
Michael Rueger a écrit :
gafisher wrote:
Showing once again the complete cluelessness of Microsoft.
Well, what do you think a third world politician (although first world ones are no different really) with no clue about technology will do given the following choices to blow 100 million $ on the OLPC:
risk it on a buggy, delayed, unproven system software or go with world wide established Windows?
Just to be sure nobody gets this wrong. This is not my opinion, I'm just stating what I think might happen...
Michael
Anything may be expected from most of the politicians also, but not different to all things of these days..........the power of the money, Whose have more money have more power....in all fields.........unfortunately.
2007/10/26, Michael Rueger michael@impara.de:
gafisher wrote:
Showing once again the complete cluelessness of Microsoft.
Well, what do you think a third world politician (although first world ones are no different really) with no clue about technology will do given the following choices to blow 100 million $ on the OLPC:
risk it on a buggy, delayed, unproven system software or go with world wide established Windows?
Just to be sure nobody gets this wrong. This is not my opinion, I'm just stating what I think might happen...
Michael
On 10/26/07, Michael Rueger michael@impara.de wrote:
risk it on a buggy, delayed, unproven system software or go with world wide established Windows?
You mean the windows that's known world wide for being buggy, delayed and proven not to work in less then perfect environments?
El 10/27/07 6:25 AM, "Jason Johnson" jason.johnson.081@gmail.com escribió:
You mean the windows that's known world wide for being buggy, delayed and proven not to work in less then perfect environments?
But 80 % of people use it. Who said the perfect is enemy of good ? I don't remember. By the way , I think Microsoft (Bill Gates) is Big Brother 2007
Edgar
squeak-dev@lists.squeakfoundation.org
-
Edgar J. De Cleene -
gafisher -
Germán Arduino -
Giovanni Corriga -
Jason Johnson -
Michael Haupt -
Michael Rueger -
nicolas cellier -
Norbert Hartl -
Philippe Marschall -
Raymond Asselin -
Tansel