WOW. It is an incredible amount of work. Really really necessary for making
Pharo more business friendly.
Thanks a lot Sven. All I wish is that you continue with it.
Cheers
On Mon, Nov 14, 2011 at 6:35 AM, Sven Van Caekenberghe wrote:
>
> On 14 Nov 2011, at 07:18, Sven Van Caekenberghe wrote:
>
On 14 Nov 2011, at 07:18, Sven Van Caekenberghe wrote:
> On 13 Nov 2011, at 23:59, Stéphane Ducasse wrote:
>
>> do you know if we should merge with the latest version in 1.4?
>
> Yes we should, the code is in a good state.
> I will make an issue because we should record the exact version that g
On 14 Nov 2011, at 02:00, mail list wrote:
> I have been very happily using ZNNeoClient.
That is good to hear.
> Does this mean that ZNClient is now the replacement for ZNNeoClient?
Yes, indeed. ZnNeoClient was the 'working title'.
Regards,
Sven
On 13 Nov 2011, at 23:59, Stéphane Ducasse wrote:
> do you know if we should merge with the latest version in 1.4?
Yes we should, the code is in a good state.
I will make an issue because we should record the exact version that got
integrated.
Sven
I have been very happily using ZNNeoClient. Does this mean that ZNClient is
now the replacement for ZNNeoClient?
Thanks
S.
On Nov 14, 2011, at 5:56 AM, Sven Van Caekenberghe wrote:
> Hi,
>
> This is a list of the most important changes to Zn since May 1st 2011:
>
> - added brand new ZnClie
thanks sven
do you know if we should merge with the latest version in 1.4?
Stef
On Nov 13, 2011, at 10:56 PM, Sven Van Caekenberghe wrote:
> Hi,
>
> This is a list of the most important changes to Zn since May 1st 2011:
>
> - added brand new ZnClient to replace all other HTTP clients (who beca
Hi,
This is a list of the most important changes to Zn since May 1st 2011:
- added brand new ZnClient to replace all other HTTP clients (who became
deprecated)
this is an object to build, execute and process HTTP client requests,
it has a rich protocol to construct requests and to access res
On 02 May 2011, at 09:51, Norbert Hartl wrote:
> Am 01.05.2011 um 21:17 schrieb Sven Van Caekenberghe:
>
>> Thanks Lukas Renggli and Marcus Denker for adding Zn to their continuous
>> integration servers.
>
> Just for the record: I have a zinc jenkins build for gemstone at
>
> https://hudson
Am 01.05.2011 um 21:17 schrieb Sven Van Caekenberghe:
> Thanks Lukas Renggli and Marcus Denker for adding Zn to their continuous
> integration servers.
Just for the record: I have a zinc jenkins build for gemstone at
https://hudson.selfish.org/job/zinc-gs/
It is triggered as soon as somethin
sven we are planning to use it for pharo in the core :).
I was just starting to do it when you got some reports so I waited a bit. I
imagine that I will do that
tomorrow evening.
Thanks for your excellent job!
Stef
On May 1, 2011, at 9:17 PM, Sven Van Caekenberghe wrote:
> Hi,
>
> It has bee
Thanks, a lot of news!
2011/5/1 Sven Van Caekenberghe :
> Hi,
>
> It has been quite a while, but here is another progress report on the Zinc
> HTTP Components project.
>
> First of all, Zinc HTTP Components has found a new home:
>
> http://zn.stfx.eu
>
> and more importantly, it is now se
Hi,
It has been quite a while, but here is another progress report on the Zinc HTTP
Components project.
First of all, Zinc HTTP Components has found a new home:
http://zn.stfx.eu
and more importantly, it is now self hosted, i.e. the pages you see are served
by Zn, and all testing and
Hey Philippe,
On 18 Dec 2010, at 17:20, Philippe Marschall wrote:
> Is the response static or do you allocate a byte array for every
> response? Despite everything this benchmark is CPU limited.
You were right: I added caching (reuse on repeated requests) on repeated
requests to my /bytes handl
On 18.12.2010 12:08, Sven Van Caekenberghe wrote:
>
> On 18 Dec 2010, at 11:30, Philippe Marschall wrote:
>
>> Benchmarks always are ;-)
>
>
> [...]
>
> Excellent writeup, once again.
>
> I think / I'm pretty confident that the cleanup goes well, as long as
> Socket[Stream] respects its time
On 18.12.2010 11:59, Sven Van Caekenberghe wrote:
>
> On 18 Dec 2010, at 09:25, Philippe Marschall wrote:
>
>> Intel(R) Core(TM)2 CPU 6600 @ 2.40GHz
>> Linux 2.6.36 (64bit)
>> Cog r2316
>> Pharo 1.1.1 (no memory tweaks)
>>
>> Basically an almost four year old Linux box.
>
> Philippe,
>
> Is t
yes but you know what I mean :)
Comanche, WebClient Swazoo
On Dec 18, 2010, at 1:51 PM, Philippe Marschall wrote:
> On 18.12.2010 11:43, Stéphane Ducasse wrote:
>> thanks philippe
>>
>> now the executive summary: does it mean that zinc is well positioned
>> compared to others?
>
> That
On 18.12.2010 11:43, Stéphane Ducasse wrote:
> thanks philippe
>
> now the executive summary: does it mean that zinc is well positioned compared
> to others?
That's a much more difficult question. First what do you mean by
"others"? Second raw performance is often not the most important
criteria
On 18 Dec 2010, at 11:30, Philippe Marschall wrote:
> Benchmarks always are ;-)
[...]
Excellent writeup, once again.
I think / I'm pretty confident that the cleanup goes well, as long as
Socket[Stream] respects its timeout (currently set at 10s for all streams,
maybe 5s would be better for
On 18 Dec 2010, at 09:25, Philippe Marschall wrote:
> Intel(R) Core(TM)2 CPU 6600 @ 2.40GHz
> Linux 2.6.36 (64bit)
> Cog r2316
> Pharo 1.1.1 (no memory tweaks)
>
> Basically an almost four year old Linux box.
Philippe,
Is that a desktop machine with a normal interactive load, or a server mac
thanks philippe
now the executive summary: does it mean that zinc is well positioned compared
to others?
Stef
On Dec 18, 2010, at 11:30 AM, Philippe Marschall wrote:
> On 18.12.2010 09:17, Stéphane Ducasse wrote:
>> Hi philippe
>>
>> thanks for helping sven. Now for the blind like me. What do
On 18.12.2010 09:17, Stéphane Ducasse wrote:
> Hi philippe
>
> thanks for helping sven. Now for the blind like me. What do the tool says?
> Because not too shabby is difficult to fully interpret :)
Benchmarks always are ;-)
Management summary it does: ~30 Mbytes/sec (bytes not bits) and 1778
req
On 17.12.2010 23:54, Sven Van Caekenberghe wrote:
> Philippe,
>
> First of all, thanks a lot for taking the time doing these benchmarks. I know
> you are very well placed to do these test, so I am honored you did.
>
> Second, although this is a static page bypassing encoding, the results are
>
Hi philippe
thanks for helping sven. Now for the blind like me. What do the tool says?
Because not too shabby is difficult to fully interpret :)
Stef
Philippe,
First of all, thanks a lot for taking the time doing these benchmarks. I know
you are very well placed to do these test, so I am honored you did.
Second, although this is a static page bypassing encoding, the results are very
impressive indeed. It is still Seaside and a 16KB page. Fur
On 15.12.2010 17:04, Sven Van Caekenberghe wrote:
> I am pleased to report another milestone was reached in the Zn project.
>
> The default implementation for an HTTP Server is now a multi-threaded
> (forking) keep-alive implementation called ZnMultiThreadedServer. It passes
> my initial concurr
Sven
our objectives is that any package published in the metacello repositories
(once metacello 1.0 is released)
should get treated by the pharo hudson server.
Eventually we want to have also the VM automatically generated.
I should learn how to set more projects :)
Stef
>> As usual, test re
On 15 Dec 2010, at 17:11, Lukas Renggli wrote:
> As usual, test results, code critics, and ready made images are available
> here:
>
> http://hudson.lukas-renggli.ch/job/Zinc/
I must say that I am quite addicted to your Hudson server, almost every time I
check in I go look at the page to
Cool, this is the way to go!
As usual, test results, code critics, and ready made images are available here:
http://hudson.lukas-renggli.ch/job/Zinc/
Lukas
On 15 December 2010 17:04, Sven Van Caekenberghe wrote:
> I am pleased to report another milestone was reached in the Zn project.
>
>
I am pleased to report another milestone was reached in the Zn project.
The default implementation for an HTTP Server is now a multi-threaded (forking)
keep-alive implementation called ZnMultiThreadedServer. It passes my initial
concurrent load tests. ZnServer is now a facade. This means that al
;)
>>> Very cool framework, I like it a lot! I definitely vote to eventually
>>> replace HTTPSocket with Zinc HTTP Components.
>>
>> I would love that.
>> We plan to open 1.3 Unstable 1 of january :)
>> So if you have code for that let me know :)
>
> Date today >= (Date year: 2011 month: 1 day:
On 08 Dec 2010, at 15:58, Stéphane Ducasse wrote:
> On Dec 8, 2010, at 10:48 AM, Lukas Renggli wrote:
>
>> Very cool framework, I like it a lot! I definitely vote to eventually
>> replace HTTPSocket with Zinc HTTP Components.
>
> I would love that.
> We plan to open 1.3 Unstable 1 of january :)
On Dec 8, 2010, at 10:48 AM, Lukas Renggli wrote:
> Very cool framework, I like it a lot! I definitely vote to eventually
> replace HTTPSocket with Zinc HTTP Components.
I would love that.
We plan to open 1.3 Unstable 1 of january :)
So if you have code for that let me know :)
>
> I wonder w
On Dec 8, 2010, at 9:26 AM, Sven Van Caekenberghe wrote:
> Norbert,
>
> Thanks for you interest.
>
> On 07 Dec 2010, at 21:14, Norbert Hartl wrote:
>
>> I scanned the code a few days ago. I tried an initial port to gemstone.
>> There are quite a few things to do. After discovering that there
On 08 Dec 2010, at 10:48, Lukas Renggli wrote:
> Very cool framework, I like it a lot! I definitely vote to eventually
> replace HTTPSocket with Zinc HTTP Components.
Thanks a lot, I am glad you like it.
> I wonder why ZnFixedClient is not a subclass of ZnHttpClient?
Well, ZnFixedClient is wha
Very cool framework, I like it a lot! I definitely vote to eventually
replace HTTPSocket with Zinc HTTP Components.
I wonder why ZnFixedClient is not a subclass of ZnHttpClient? I think
it would be cool to be able to use them polymorphic.
Lukas
On 8 December 2010 09:26, Sven Van Caekenberghe w
Norbert,
Thanks for you interest.
On 07 Dec 2010, at 21:14, Norbert Hartl wrote:
> I scanned the code a few days ago. I tried an initial port to gemstone. There
> are quite a few things to do. After discovering that there are really big
> changes from version to version and the existence of cl
I scanned the code a few days ago. I tried an initial port to gemstone. There
are quite a few things to do. After discovering that there are really big
changes from version to version and the existence of classes with suffixes Old
and New made me stop the effort. I'm really missing a usable http
This is another progress report on the Zinc HTTP Components project.
- I finally integrated support for UTF-8 encoding and decoding of text entities
(ZnStringEntity, ZnUTF8Encoder).
- Internally, all input and output is done through binary streams (but
character streams are still supported for d
Matt Sven I love to see your framework emerging like that.
Keep pushing. This is a warm feeling for us (with our head in the gory details
of the system) so see that other people
are creating cool abstractions on top of it.
Stef
> Hi everyone,
>
> On Oct 1, 2010, at 8:10 AM, Lukas Renggli wrot
Hi everyone,
On Oct 1, 2010, at 8:10 AM, Lukas Renggli wrote:
> Wow, very impressive.
>
> What I would like to see is some kind of high-level API for convenient
> access to all features. Something along
>
> response := ZnHttp new
>url: 'http://www.foo.com';
>userAgent: 'FakeAgent';
>
>> response := ZnHttp new
>> url: 'http://www.foo.com';
>> userAgent: 'FakeAgent';
>> cookieAt: 'something' put: '123';
>> parameterAt: 'q' put: 'smalltalk';
>> onFailure: [ :error | self inform: 'failed' ];
>> onProgress: [ :status | ... ];
>> get
>
> A bit like Gofer I guess.
Lukas,
On 01 Oct 2010, at 14:10, Lukas Renggli wrote:
> What I would like to see is some kind of high-level API for convenient
> access to all features. Something along
>
> response := ZnHttp new
>url: 'http://www.foo.com';
>userAgent: 'FakeAgent';
>cookieAt: 'something' put: '123';
Wow, very impressive.
What I would like to see is some kind of high-level API for convenient
access to all features. Something along
response := ZnHttp new
url: 'http://www.foo.com';
userAgent: 'FakeAgent';
cookieAt: 'something' put: '123';
parameterAt: 'q' put: 'smalltalk';
o
Cool!
Stef
On Oct 1, 2010, at 10:04 AM, Sven Van Caekenberghe wrote:
> Here is a quick progress report regarding the Zinc HTTP Components project.
> Please check the SqueakSource history for a all the details.
> The external documentation has not yet been updated ;-)
>
> I am very pleased that
Here is a quick progress report regarding the Zinc HTTP Components project.
Please check the SqueakSource history for a all the details.
The external documentation has not yet been updated ;-)
I am very pleased that Matt Kennedy joined the project as a developer and
is contributing lots of really
45 matches
Mail list logo
