[Pharo-users] Re: is there a better way

To avoid doing something like that, and for a web scrapping tool I wrote, I implemented a basic subclass of ZnClient (called ZnCachingClient) that used a disk cache where each key/file was the hash of the requested URL. I haven't used in a while but it should continue to work, in any case, I

[Pharo-users] Re: is there a better way

Op 6-1-2021 om 19:36 schreef Richard Sargent: On Wed, Jan 6, 2021 at 10:34 AM Roelof Wobben via Pharo-users wrote: Thanks,

[Pharo-users] Re: is there a better way

On Wed, Jan 6, 2021 at 10:34 AM Roelof Wobben via Pharo-users < pharo-users@lists.pharo.org> wrote: > > Thanks, > > Right now im downloading/fetching the images every time again. > > As I see it, the biggest bottleneck is that I have 10 images. > And for all 10 I fetching the image and the data I

[Pharo-users] Re: is there a better way

Thanks, Right now im downloading/fetching the images every time again. As I see it, the biggest bottleneck is that I have 10 images. And for all 10 I fetching the image and the data I could display when a user wants it. So that will be 20 calls to the api. So maybe some cache could be

[Pharo-users] Re: NeoCSVReader and wrong number of fieldAccessors

You aren't sure what point I was making? How about the one I actually wrote down: What test data was NeoCSV benchmarked with and can I get my hands on it? THAT is the point. The data points I showed (and many others I have not) are not satisfactory to me. I have been searching for CSV test

[Pharo-users] Re: NeoCSVReader and wrong number of fieldAccessors

Richard, Am 07.01.21 um 07:15 schrieb Richard O'Keefe: You aren't sure what point I was making? exactly, the thread you answered was about a possible bug in NeoCSV parser. Your post was about your doubts about the claim of efficiency on the parser's web site. So you threw in some

[Pharo-users] Re: NeoCSVReader and wrong number of fieldAccessors

John I’m sorry to tell you that but you cannot write mail like that without telling us where is the code of CVSParser. You cannot basically discredit the work on Sven without providing code to compare. S. > On 6 Jan 2021, at 05:10, Richard O'Keefe wrote: > > NeoCSVReader is described as

[Pharo-users] Re: NeoCSVReader and wrong number of fieldAccessors

Another point: In open-source and in this community. Either the code people mentioned is open-source and accessible or it does not exist. If it does not exist then this is easy :) S. > On 6 Jan 2021, at 05:10, Richard O'Keefe wrote: > > NeoCSVReader is described as efficient. What is that

[Pharo-users] Re: NeoCSVReader and wrong number of fieldAccessors

Hi Richard, Benchmarking is a can of worms, many factors have to be considered. But the first requirement is obviously to be completely open over what you are doing and what you are comparing. NeoCSV contains a simple benchmark suite called NeoCSVBenchmark, which was used during development.

[Pharo-users] [ANN] Superluminal v1.2.1 [v1.2.1] released!

Superluminal, building blocks for creating HTTP requests and API clients reached it's v1.2.1 version. Changelog Fixed #31: Improving Expires error handling during parsing to be consistent with RFC 7234. Thanks @nchillo PR #29: Make RESTfulAPIClient>>#getAt:configuredBy:withSuccessfulResponseDo:

[Pharo-users] Re: NeoCSVReader and wrong number of fieldAccessors

Richard, I am not sure what point you are trying to make here. You have something cooler and faster? Great, how about sharing? You could make a faster one when it doesn't convert numbers and stuff? Great. I guess the time will be spent after parsing in 95% of the use cases. It depends. And

[Pharo-users] Re: NeoCSVReader and wrong number of fieldAccessors

Hi Sven, I must say I am really happy with your change. We get a nice exception whenever the number of fieldAccessor doesn't match with the number of defined fieldAccessors. So far it also seems the endless loops are gone as well. What a leap forward! I'm adding an issue on github about

[Pharo-users] Re: NeoCSVReader and wrong number of fieldAccessors

Joachim, > On 6 Jan 2021, at 11:21, jtuc...@objektfabrik.de wrote: > > Hi Sven, > > > I must say I am really happy with your change. We get a nice exception > whenever the number of fieldAccessor doesn't match with the number of defined > fieldAccessors. So far it also seems the endless

[Pharo-users] Re: is there a better way

Roelof, Working with multiple high resolution images, as I believe you are doing, is always going to be a real challenge, performance wise. It just takes time to transfer lots of data. First you have to make sure that you are not doing too much work (double downloads, using too high

[Pharo-users] [Pharo @ FOSDEM 2021] Stand

We applied to participate in FOSDEM 2021, and we were accepted :)! === Hello team behind Pharo, Your submission for a stand at FOSDEM 2021 has been accepted. We welcome you to FOSDEM 2021, our first fully digital edition. As a reminder, this is what you can

[Pharo-users] Re: [Pharo @ FOSDEM 2021] Stand

Hello everybody. We have been accepted to have a virtual stand in FOSDEM 2021. The idea is to start gathering information to show in the stand about Pharo. Besides the pharo graphical image related content, we would like to offer also success stories, and also videos related to your tools / fwks

[Pharo-users] [ANN] Stargate-Consul v2.0.0 [v2.0.0] released!

Stargate-Consul, integration with Consul HTTP API to register and deregister services reached it's v2.0.0 version. Changelog Use GitHub Actions to run the build and the integration tests Add a docker package with an example application Use Pharo 8 as the base image for docker to run the