On Monday, 4 January 2016 at 17:02:01 UTC, Sönke Ludwig wrote:
> ...Maybe it's something specific to your OS/Chrome version?

Well, I tried again on the same machine but using Firefox and it worked, then I tried on my Tablet (Android/KitKat) using both Chrome and Native Browser and worked too.

So I think It's something going wrong with Chrome here!

Bubba.

Am 04.01.2016 um 16:20 schrieb Charles:
> On Monday, 4 January 2016 at 10:19:52 UTC, Sönke Ludwig wrote:
>> Finally published the article that I had prepared in autumn last year.
>> It gives an overview of the basic functionality needed to implement a
>> typical web application using vibe.d. The example uses Redis as a data
>> store - using other storage solutions may be a good topic for a
>> follow-up article.
>>
>> https://vibed.org/blog/posts/a-scalable-chat-room-service-in-d
>>
>> Reddit:
>> https://www.reddit.com/r/programming/comments/3ze948/writing_a_scalable_chat_room_service_in_d/
>>
>
> Wish I knew this was being worked on. I had something similar over at:
> http://wiki.dlang.org/User:Csmith1991/Vibe.d_Documentation/websocket

Oh, that indeed looks painfully similar. In any case, I'll link to it from the tutorials section. It uses the lower level APIs, so it's still interesting as an alternative implementation approach.

bad links in tutorial:

https://vibed.org/blog/posts/a-scalable-chat-room-service-in-d/vibe-web

registerWebInterface is the entry point to vibe.d's high-level web application framework. It takes a class instance and registers each of its public methods as a route in the URLRouter. By default, the method names are mapped to

I wonder if you could add a feature to vibe.d that checks for links that are out-dated? Maybe, ultimate, attempt to search for "feasible" substitutions instead of a 404 and present them to the user? Everyone hates 404's, right?

Am 04.01.2016 um 18:33 schrieb Jason Jeffory:
> bad links in tutorial:
>
> https://vibed.org/blog/posts/a-scalable-chat-room-service-in-d/vibe-web
>
> registerWebInterface is the entry point to vibe.d's high-level web
> application framework. It takes a class instance and registers each of
> its public methods as a route in the URLRouter. By default, the method
> names are mapped to

Thanks, fixed now.

>
> I wonder if you could add a feature to vibe.d that checks for links that
> are out-dated? Maybe, ultimate, attempt to search for "feasible"
> substitutions instead of a 404 and present them to the user? Everyone
> hates 404's, right?

That would be difficult to do in the general case. Here, the mistake was in the Markdown syntax ([application framework](vibe-web) instead of [application framework][vibe-web]). Something to detect this could indeed be nicely built into the blog engine, but as a generic vibe.d feature it would be rather difficult to integrate in a nice way.

On Monday, 4 January 2016 at 10:19:52 UTC, Sönke Ludwig wrote:
> Finally published the article that I had prepared in autumn last year. It gives an overview of the basic functionality needed to implement a typical web application using vibe.d. The example uses Redis as a data store - using other storage solutions may be a good topic for a follow-up article.
>
> https://vibed.org/blog/posts/a-scalable-chat-room-service-in-d
>
> Reddit: https://www.reddit.com/r/programming/comments/3ze948/writing_a_scalable_chat_room_service_in_d/

This article seems what a lot of people on Hacker News would go for. Do you plan to submit it there as well?

Am 04.01.2016 um 20:39 schrieb Meta:
> On Monday, 4 January 2016 at 10:19:52 UTC, Sönke Ludwig wrote:
>> Finally published the article that I had prepared in autumn last year.
>> It gives an overview of the basic functionality needed to implement a
>> typical web application using vibe.d. The example uses Redis as a data
>> store - using other storage solutions may be a good topic for a
>> follow-up article.
>>
>> https://vibed.org/blog/posts/a-scalable-chat-room-service-in-d
>>
>> Reddit:
>> https://www.reddit.com/r/programming/comments/3ze948/writing_a_scalable_chat_room_service_in_d/
>>
>
> This article seems what a lot of people on Hacker News would go for. Do
> you plan to submit it there as well?

If it fits, I definitely wouldn't mind that. I just don't have an account there, so if someone who does could post it that'd be nice. Otherwise I can create one, too, of course.

Am 04.01.2016 um 21:21 schrieb Sönke Ludwig:
> Am 04.01.2016 um 20:39 schrieb Meta:
>> On Monday, 4 January 2016 at 10:19:52 UTC, Sönke Ludwig wrote:
>>> Finally published the article that I had prepared in autumn last year.
>>> It gives an overview of the basic functionality needed to implement a
>>> typical web application using vibe.d. The example uses Redis as a data
>>> store - using other storage solutions may be a good topic for a
>>> follow-up article.
>>>
>>> https://vibed.org/blog/posts/a-scalable-chat-room-service-in-d
>>>
>>> Reddit:
>>> https://www.reddit.com/r/programming/comments/3ze948/writing_a_scalable_chat_room_service_in_d/
>>>
>>>
>>
>> This article seems what a lot of people on Hacker News would go for. Do
>> you plan to submit it there as well?
>
> If it fits, I definitely wouldn't mind that. I just don't have an
> account there, so if someone who does could post it that'd be nice.
> Otherwise I can create one, too, of course.

Has actually already been posted a few hours ago (at pos. 302. currently, though).

Am Mon, 04 Jan 2016 17:15:36 +0000
schrieb Bubbasaur <bubba@gmail.com>:

> On Monday, 4 January 2016 at 17:02:01 UTC, Sönke Ludwig wrote:
> > ...Maybe it's something specific to your OS/Chrome version?
> 
> Well, I tried again on the same machine but using Firefox and it worked, then I tried on my Tablet (Android/KitKat) using both Chrome and Native Browser and worked too.
> 
> So I think It's something going wrong with Chrome here!
> 
> Bubba.

IIRC the letsencrypt people said in their 32c3 talk* that there might still be some issues with chrome. (chrome is probably caching something it shouldn't cache. Try clearing all caches)

[*] https://media.ccc.de/v/32c3-7528-let_s_encrypt_--_what_launching_a_free_ca_looks_like