Hi Alexandre,
I'll try to answer as good as I can, please excuse if I got part of your
question wrong. So I see two parts that can be slow:
1. The application runtime performance. Due to additional debug checks
and less optimization, debug builds will run slower than release builds,
but
Am 04.11.2013 18:35, schrieb Dicebot:
On Monday, 4 November 2013 at 16:40:25 UTC, Alexandre Riveira wrote:
Hi Sönke,
Congratulations for your hard work.
One question,
How do you think your framework running in development mode where a
huge amount of models with many business rules exist. A
Hi Sönke,
My concern is actually in development time. Compilation,
debugging, etc.. Ruby on rails applications had their reload
classes optimized effecting only reload the classes changed
instead of the entire environment. Today we have the application
of ERP type integrated e-commerce with
Hi Sönke,
Congratulations for your hard work.
One question,
How do you think your framework running in development mode where
a huge amount of models with many business rules exist. A system
under development can be slow, like java where a signature change
in the method requires reload of
On Monday, 4 November 2013 at 16:40:25 UTC, Alexandre Riveira
wrote:
Hi Sönke,
Congratulations for your hard work.
One question,
How do you think your framework running in development mode
where a huge amount of models with many business rules exist. A
system under development can be slow,
On Monday, 4 November 2013 at 16:40:25 UTC, Alexandre Riveira
wrote:
Hi Sönke,
Congratulations for your hard work.
One question,
How do you think your framework running in development mode
where a huge amount of models with many business rules exist. A
system under development can be slow,
How do a manual install on linux ?
I am a fedora user they are no specialized or common install
documentation!
On Monday, 7 May 2012 at 18:51:26 UTC, Sönke Ludwig wrote:
I think one of us (Jan) has something for better form handling
locally, not yet committed, and I would count that as something
that would still fit well into the core package. But in
general, I think the number of features should not
I'm currently building a site in vibe and love it. There are
still a few bugs around, and a few useful features to come, but
I've been patching and writing features as I go, so its all good.
I am curious about your policy on big features though, I have
been working an implementation for using
Am 03.05.2012 00:18, schrieb bls:
Am 01.05.2012 23:46, schrieb Sönke Ludwig:
I made a post with Steve Teale's MySQL driver as an example:
http://vibed.org/blog/posts/writing-native-db-drivers
There were some hidden gotchas, but I hope the current port doesn't
break anything from the original
Am 30.04.2012 08:38, schrieb Sönke Ludwig:
If you mean automatic generation of a REST interface for an existing D
interface, then it's definitely planned. I can imagine a sloppy version
where the HTTP method is always POST or can be POST/GET as desired by
the client. But I would also like to
Am 03.05.2012 11:22, schrieb bls:
Should be POST GET PUT DELETE
I would be fantastic if vibe.d can implement a REST SERVER following
this guideline :
A very interesting read regarding implementing a rest server (PHP)
http://www.gen-x-design.com/archives/create-a-rest-api-with-php/
Bjoern
On Wednesday, 2 May 2012 at 22:18:12 UTC, bls wrote:
Am 01.05.2012 23:46, schrieb Sönke Ludwig:
I made a post with Steve Teale's MySQL driver as an example:
http://vibed.org/blog/posts/writing-native-db-drivers
There were some hidden gotchas, but I hope the current port
doesn't
break
I've been playing around with vibe in my free time the last few
days, and here are the beginnings of a stab at REST:
https://github.com/csauls/zeal.d/blob/master/source/zeal/http/router.d
Admittedly it rips off the Rails way of recognizing and pathing
the REST actions, but I admit a small bias
On Thursday, 3 May 2012 at 09:22:23 UTC, bls wrote:
Should be POST GET PUT DELETE
I'm afraid, some proxies may cut unusual http verbs. SVN relies
on them and if a proxy is not nice, it gets broken.
Am 01.05.2012 23:46, schrieb Sönke Ludwig:
I made a post with Steve Teale's MySQL driver as an example:
http://vibed.org/blog/posts/writing-native-db-drivers
There were some hidden gotchas, but I hope the current port doesn't
break anything from the original code.
Looks good. Unfortunately I
Am Mon, 30 Apr 2012 15:52:36 -0700
schrieb Sean Kelly s...@invisibleduck.org:
On Apr 30, 2012, at 8:26 AM, Sönke Ludwig wrote:
Am 30.04.2012 15:48, schrieb Sean Kelly:
On Apr 30, 2012, at 1:03 AM, Sönke Ludwig wrote:
Am 27.04.2012 16:50, schrieb Sean Kelly:
In _d_throw call abort().
Am 29.04.2012 08:13, schrieb bls:
Great job. Thanks Soenke et al;
- Built-in support for MongoDB and Redis databases
MySQL.
Like other folks here I need a SQL db, At least for MyQL 5.1 there is a
socket based solution from Steve Teale.
https://github.com/britseye/mysqln
Means no licence
On Tuesday, 1 May 2012 at 21:46:42 UTC, Sönke Ludwig wrote:
I made a post with Steve Teale's MySQL driver as an example:
http://vibed.org/blog/posts/writing-native-db-drivers
There were some hidden gotchas, but I hope the current port
doesn't break anything from the original code.
The table
On Tue, May 1, 2012 at 5:04 PM, Matt Peterson ricoche...@gmail.com wrote:
On Tuesday, 1 May 2012 at 21:46:42 UTC, Sönke Ludwig wrote:
I made a post with Steve Teale's MySQL driver as an example:
On 2012-04-29 20:29, Sönke Ludwig wrote:
You just don't have to care about how to parse command line arguments,
how to initialize the library and to start the event loop.
Right, didn't thought of that. Would it be a good idea to allow top
level code and use import and mixin the code in some
Am 29.04.2012 23:41, schrieb bls:
Seems that my last reply was jammned or whatever .. so in short
x509 certificate support... Why not ?
Do you mean for SSL or package signing or something else? They are
currently used for SSL, but currently there is no certificate validation
on the client
Am 29.04.2012 21:57, schrieb Mirko Pilger:
i would like to know a bit more about those extension modules for vibe
and the vpm registry. e.g. can i write yet another web framework on
top of the vibe io modules as an vibe extension and would you even
encourage this?
Essentially a VPM module
Am 30.04.2012 08:22, schrieb Jacob Carlborg:
On 2012-04-29 20:29, Sönke Ludwig wrote:
You just don't have to care about how to parse command line arguments,
how to initialize the library and to start the event loop.
Right, didn't thought of that. Would it be a good idea to allow top
level
Am 28.04.2012 20:47, schrieb Rory McGuire:
Awesome! that was one of my concerns with D in general with server
software and its long running nature.
I've been thinking about fibers and socket.d this week. Glad you
anounced this before I started working on something :D.
Yeah I've also tought
Am 27.04.2012 16:50, schrieb Sean Kelly:
In _d_throw call abort(). That'll give you a core file.
Thanks, I've tracked it down to an assertion by logging stderr for now,
but next time I will try the abort method (with __d_assert*), because
just a call stack without line numbers was a bit
On Mon, Apr 30, 2012 at 9:57 AM, Sönke Ludwig slud...@outerproduct.orgwrote:
How difficult would it be for you to split the async IO parts into a
separate library? This would be very much like gevent (python:
http://www.gevent.org/).
That would basically be vibe.core and vibe.stream. Those
On 2012-04-30 09:00, Sönke Ludwig wrote:
Interesting haven't thought about going that far :)
Somehow that reminds me of:
#define IF if(
#define THEN ){
#define ELSE } else {
#define ENDIF }
to transform C into BASIC. The scripting-only people would probably be
thrilled ;) But I have the
On Monday, 30 April 2012 at 09:14:31 UTC, Jacob Carlborg wrote:
On 2012-04-30 09:00, Sönke Ludwig wrote:
They will also soon wonder why they cannot put
top-level code in their other files.
Yeah, I guess that will most likely be a problem.
Also, doesn't ImportExpression require passing -J to
On 2012-04-30 13:05, David Nadlinger wrote:
On Monday, 30 April 2012 at 09:14:31 UTC, Jacob Carlborg wrote:
On 2012-04-30 09:00, Sönke Ludwig wrote:
They will also soon wonder why they cannot put
top-level code in their other files.
Yeah, I guess that will most likely be a problem.
Also,
On Apr 30, 2012, at 1:03 AM, Sönke Ludwig wrote:
Am 27.04.2012 16:50, schrieb Sean Kelly:
In _d_throw call abort(). That'll give you a core file.
Thanks, I've tracked it down to an assertion by logging stderr for now, but
next time I will try the abort method (with __d_assert*), because
Am 30.04.2012 15:48, schrieb Sean Kelly:
On Apr 30, 2012, at 1:03 AM, Sönke Ludwig wrote:
Am 27.04.2012 16:50, schrieb Sean Kelly:
In _d_throw call abort(). That'll give you a core file.
Thanks, I've tracked it down to an assertion by logging stderr for now, but
next time I will try the
On Mon, 30 Apr 2012 17:26:54 +0200, Sönke Ludwig
slud...@outerproduct.org wrote:
Am 30.04.2012 15:48, schrieb Sean Kelly:
On Apr 30, 2012, at 1:03 AM, Sönke Ludwig wrote:
Am 27.04.2012 16:50, schrieb Sean Kelly:
In _d_throw call abort(). That'll give you a core file.
Thanks, I've
On Apr 30, 2012, at 8:26 AM, Sönke Ludwig wrote:
Am 30.04.2012 15:48, schrieb Sean Kelly:
On Apr 30, 2012, at 1:03 AM, Sönke Ludwig wrote:
Am 27.04.2012 16:50, schrieb Sean Kelly:
In _d_throw call abort(). That'll give you a core file.
Thanks, I've tracked it down to an assertion by
Great job. Thanks Soenke et al;
- Built-in support for MongoDB and Redis databases
MySQL.
Like other folks here I need a SQL db, At least for MyQL 5.1
there is a socket based solution from Steve Teale.
https://github.com/britseye/mysqln
Means no licence trouble, and probably easier to
Am 29.04.2012 06:18, schrieb Martin Nowak:
Very nice to see that someone took the async/Fiber idea that far.
Some observations:
- Wouldn't wrapping code in void main() instead of static this()
make better front page examples.
The static this() pattern is mainly there to appeal to users of
Am 29.04.2012 08:13, schrieb bls:
Great job. Thanks Soenke et al;
- Built-in support for MongoDB and Redis databases
MySQL.
Like other folks here I need a SQL db, At least for MyQL 5.1 there is a
socket based solution from Steve Teale.
https://github.com/britseye/mysqln
Means no licence
On Sun, 29 Apr 2012 08:13:40 +0200, bls b...@orange.fr wrote:
There is also a socket based PostgreSQL driver available, but I have
lost the link and dunno about the status quo.
This? https://github.com/pszturmaj/ddb
On Sun, 29 Apr 2012 10:31:07 +0200, Sönke Ludwig
slud...@outerproduct.org wrote:
Quote
Additional drivers are easy to port to vibe.d because of the blocking
API - basically the only thing that has to be done is to replace the
socket calls (send(), recv(), connect() etc.) with the
On 2012-04-29 10:07, Sönke Ludwig wrote:
The static this() pattern is mainly there to appeal to users of similar
systems in script languages, where you don't have a main function at all
and just happily hack away. For larger projects it doesn't make a
difference but for small projects it can
Am 29.04.2012 11:52, schrieb simendsjo:
On Sun, 29 Apr 2012 10:31:07 +0200, Sönke Ludwig
slud...@outerproduct.org wrote:
Quote
Additional drivers are easy to port to vibe.d because of the blocking
API - basically the only thing that has to be done is to replace the
socket calls (send(),
Am 29.04.2012 15:22, schrieb Jacob Carlborg:
On 2012-04-29 10:07, Sönke Ludwig wrote:
The static this() pattern is mainly there to appeal to users of similar
systems in script languages, where you don't have a main function at all
and just happily hack away. For larger projects it doesn't make
i would like to know a bit more about those extension modules for vibe
and the vpm registry. e.g. can i write yet another web framework on
top of the vibe io modules as an vibe extension and would you even
encourage this?
On Sunday, 29 April 2012 at 08:52:09 UTC, simendsjo wrote:
On Sun, 29 Apr 2012 08:13:40 +0200, bls b...@orange.fr wrote:
There is also a socket based PostgreSQL driver available, but
I have lost the link and dunno about the status quo.
This? https://github.com/pszturmaj/ddb
Exactly.
On Sun, 29 Apr 2012 20:28:38 +0200, Sönke Ludwig
slud...@outerproduct.org wrote:
It was a bug in the RSS generator. I just added the article without
content to not forget about it but didn't publish it yet. The RSS
generator, however, published it anyway.
Yeah, I was pretty quick to find
Am 28.04.2012 06:16, schrieb Ary Manzana:
On 4/28/12 8:12 AM, Ary Manzana wrote:
On 4/27/12 4:46 AM, Sönke Ludwig wrote:
During the last few months, we have been working on a new
framework for general I/O and especially for building
extremely fast web apps. It combines asynchronous I/O with
[my previous anwer got lost because of an high-load error on the NG
server. hope I didn't forget anything..]
Am 27.04.2012 21:40, schrieb F i L:
Sönke Ludwig wrote:
During the last few months, we have been working on a new
framework for general I/O and especially for building
extremely fast
Am 27.04.2012 11:34, schrieb Sönke Ludwig:
I'm starting to monitor it now. Directly after startup, the website is
at 32 MB. The traffic has dropped a bit but hopefully it's enough to see
something if there is a hidden leak.
A mid-term test now shows that shortly after startup the virtual
Awesome! that was one of my concerns with D in general with server software
and its long running nature.
I've been thinking about fibers and socket.d this week. Glad you anounced
this before I started working on something :D.
How difficult would it be for you to split the async IO parts into a
Very nice to see that someone took the async/Fiber idea that far.
Some observations:
- Wouldn't wrapping code in void main() instead of static this() make
better front page examples.
- It would be interesting to know what made you write your own Stream/JSON
implementations.
- I think there
Am 26.04.2012 23:59, schrieb bearophile:
Sönke Ludwig:
See http://vibed.org/ for more information and some example
I see the code:
import vibe.d;
...
static this()
{
listenTcp(7, (conn){ conn.write(conn) });
}
Isn't it better to use this?
import vibe.all;
And in the last line is a
On Friday, 27 April 2012 at 02:19:23 UTC, Andrei Alexandrescu
wrote:
On 4/26/12 3:30 PM, Jesse Phillips wrote:
On Thursday, 26 April 2012 at 22:05:29 UTC, Robert Clipsham
wrote:
On 26/04/2012 21:46, Sönke Ludwig wrote:
vibe.d
This looks awesome!
Also on reddit:
Am 27.04.2012 04:19, schrieb Andrei Alexandrescu:
On 4/26/12 3:30 PM, Jesse Phillips wrote:
On Thursday, 26 April 2012 at 22:05:29 UTC, Robert Clipsham wrote:
On 26/04/2012 21:46, Sönke Ludwig wrote:
vibe.d
This looks awesome!
Also on reddit:
On 2012-04-26 22:46, Sönke Ludwig wrote:
During the last few months, we have been working on a new
framework for general I/O and especially for building
extremely fast web apps. It combines asynchronous I/O with
core.thread's great fibers to build a convenient, blocking
API which can handle
Great work!
This is the the type of server side frameworks we need.
--
Paulo
On Thursday, 26 April 2012 at 20:46:41 UTC, Sönke Ludwig wrote:
During the last few months, we have been working on a new
framework for general I/O and especially for building
extremely fast web apps. It combines
On Thursday, 26 April 2012 at 20:46:41 UTC, Sönke Ludwig wrote:
During the last few months, we have been working on a new
framework for general I/O and especially for building
extremely fast web apps. It combines asynchronous I/O with
core.thread's great fibers to build a convenient, blocking
I had to copy the included .lib files into bin in order to build the
examples but so far, so good. This is awesome.
Regards,
Brad Anderson
There is some really strange behavior of Windows batch files where it
sometimes fails with environment variables set with quotes and sometimes
On Friday, 27 April 2012 at 07:00:23 UTC, Sönke Ludwig wrote:
I had to copy the included .lib files into bin in order to
build the
examples but so far, so good. This is awesome.
Regards,
Brad Anderson
There is some really strange behavior of Windows batch files
where it sometimes fails
Am 27.04.2012 09:08, schrieb Brad Anderson:
On Friday, 27 April 2012 at 07:00:23 UTC, Sönke Ludwig wrote:
I had to copy the included .lib files into bin in order to build the
examples but so far, so good. This is awesome.
Regards,
Brad Anderson
There is some really strange behavior of
Sounds great! And the site's very speedy :) I'm especially excited about
this:
(Work-in-progress) An integrated load balancer is able to dynamically
compile, run and test new processes before switching them live after the
code has been modified.
A few questions:
- Does the web framework
Sönke Ludwig wrote:
During the last few months, we have been working on a new
framework for general I/O and especially for building
extremely fast web apps. It combines asynchronous I/O with
core.thread's great fibers to build a convenient, blocking
API which can handle insane amounts of
Am 27.04.2012 10:01, schrieb Nick Sabalausky:
Sounds great! And the site's very speedy :) I'm especially excited about
this:
(Work-in-progress) An integrated load balancer is able to dynamically
compile, run and test new processes before switching them live after the
code has been modified.
On 04/27/2012 10:01 AM, Nick Sabalausky wrote:
...
- Why static this? Seems like a strange choice since it'll run before the
main that (I assume) vibed automatically provides - and in an undefined
order relative to all other module ctors.
This is not true. The order is defined as far it
Am 27.04.2012 10:10, schrieb Dmitry Olshansky:
On 27.04.2012 0:46, Sönke Ludwig wrote:
During the last few months, we have been working on a new
framework for general I/O and especially for building
extremely fast web apps. It combines asynchronous I/O with
core.thread's great fibers to build a
Am 27.04.2012 10:16, schrieb David Nadlinger:
On Thursday, 26 April 2012 at 22:25:33 UTC, Vladimir Panteleev wrote:
On Thursday, 26 April 2012 at 20:46:41 UTC, Sönke Ludwig wrote:
During the last few months, we have been working on a new
framework for general I/O and especially for building
Sönke Ludwig slud...@outerproduct.org wrote in message
news:jndl9l$26eh$1...@digitalmars.com...
We still have a more comprehensive benchmark on the table but it seemed to
get along happily with about 60MB of RAM usage during a C10k test. The
average request time went down to about 6s if I
Am 27.04.2012 11:06, schrieb Nick Sabalausky:
Sönke Ludwigslud...@outerproduct.org wrote in message
news:jndl9l$26eh$1...@digitalmars.com...
We still have a more comprehensive benchmark on the table but it seemed to
get along happily with about 60MB of RAM usage during a C10k test. The
Am 27.04.2012 10:26, schrieb Andrej Mitrovic:
On 4/27/12, Sönke Ludwigslud...@outerproduct.org wrote:
Now I changed the line SET LIBDIR=..\lib\win-i386 in run_example.cmd
from quoted to non-quoted and for me it seems to work.
Maybe try:
SET LIBDIR=..\lib\win-i386
IOW quotes after SET.
I am not sure if you're aware of Flask, Flask is a microframework for
Python.
It provides something called Blueprints, you can register e.g.
routes to this Blueprint and to use them you've to add them to the
main application. This makes code way more readable!
Also some kind of after_request
Can't wait to go home and get my greedy hands on it.
Sounds.. amazing. Hell, if all of this stuff really works and
works on par with nginx+fastcgi performance, it can be the very
killer app for D waited so long.
Excellent work Sönke! Vibe.d seems very promising :)
I've played with vibe.d with a hello project as described in the
document, and downloaded vibenotes and vibeblog from git and
poked around a little.
vibe.d gives me a very smooth experience, and I'll try learn
about it more :)
two little
Am 27.04.2012 11:57, schrieb David:
I am not sure if you're aware of Flask, Flask is a microframework for
Python.
It provides something called Blueprints, you can register e.g.
routes to this Blueprint and to use them you've to add them to the
main application. This makes code way more
Am 27.04.2012 13:07, schrieb Puming:
Excellent work Sönke! Vibe.d seems very promising :)
Thanks :)
I've played with vibe.d with a hello project as described in the
document, and downloaded vibenotes and vibeblog from git and
poked around a little.
vibe.d gives me a very smooth experience,
Am 27.04.2012 13:18, schrieb Sönke Ludwig:
Am 27.04.2012 11:57, schrieb David:
I am not sure if you're aware of Flask, Flask is a microframework for
Python.
It provides something called Blueprints, you can register e.g.
routes to this Blueprint and to use them you've to add them to the
main
On Friday, 27 April 2012 at 08:47:23 UTC, Sönke Ludwig wrote:
Initially I wanted to have a page-comment feature ready as on
dlang.org. But for now I guess the github issue tracker should
do the job: https://github.com/rejectedsoftware/vibe.d/issues
Oh, and another thing, is vpm live yet? I
Am 27.04.2012 13:57, schrieb David Nadlinger:
On Friday, 27 April 2012 at 08:47:23 UTC, Sönke Ludwig wrote:
Initially I wanted to have a page-comment feature ready as on
dlang.org. But for now I guess the github issue tracker should do the
job: https://github.com/rejectedsoftware/vibe.d/issues
Sönke, vibed is truly amazing! I am interested in the web server's internal
architecture. I always wanted to do an implementation of a web server using
a form of asymmetric, multi-process event-driven architecture. A web server
which utilises fibers. It would be nice if you explain the
Am 26.04.2012 23:54, schrieb Trass3r:
Looks promising.
Though I wouldn't know how to choose between Adam's web framework,
Cybershadow's code (seemed like he coded the newsreader in no time and
it works very nicely) and yours.
Any advice?
I guess it just comes down to tast and requirements. If
The server is back up and I've looked at Flask's blueprints. So they
have a more implicit approach with annotations (once D has these, it
would be a possible extension for vibe). Right now my corresponding
pattern looks like this:
// create a global url router
auto r = new UrlRouter
//
In _d_throw call abort(). That'll give you a core file.
On Apr 26, 2012, at 11:13 PM, Sönke Ludwig slud...@outerproduct.org wrote:
Am 27.04.2012 04:19, schrieb Andrei Alexandrescu:
On 4/26/12 3:30 PM, Jesse Phillips wrote:
On Thursday, 26 April 2012 at 22:05:29 UTC, Robert Clipsham wrote:
On 27-04-2012 16:50, Sean Kelly wrote:
In _d_throw call abort(). That'll give you a core file.
On Apr 26, 2012, at 11:13 PM, Sönke Ludwigslud...@outerproduct.org wrote:
Am 27.04.2012 04:19, schrieb Andrei Alexandrescu:
On 4/26/12 3:30 PM, Jesse Phillips wrote:
On Thursday, 26 April 2012
Sönke Ludwig:
The import vibe.d; is actually just a play on the frameworks
name and just should be easy to remember. In addition to
importing all modules, it also imports a module containing the
main function, so this is a special beast. But there is
actually a import vibe.vibe; which is the
On Friday, 27 April 2012 at 15:26:02 UTC, bearophile wrote:
But isn't .all a kind of standard D convention (that is
better to generally use)? (I am not sure).
No, not at this point. Some people prefer somepackage._, and
there recently has been a proposal by Andrei (DIP16) to allow a
special
On Apr 27, 2012, at 1:27 AM, Sönke Ludwig slud...@outerproduct.org wrote:
We still have a more comprehensive benchmark on the table but it seemed to
get along happily with about 60MB of RAM usage during a C10k test. The
average request time went down to about 6s if I remember correctly. The
Am 27.04.2012 18:54, schrieb Sean Kelly:
On Apr 27, 2012, at 1:27 AM, Sönke Ludwigslud...@outerproduct.org wrote:
We still have a more comprehensive benchmark on the table but it seemed to get
along happily with about 60MB of RAM usage during a C10k test. The average
request time went down
Sönke Ludwig wrote:
During the last few months, we have been working on a new
framework for general I/O and especially for building
extremely fast web apps. It combines asynchronous I/O with
core.thread's great fibers to build a convenient, blocking
API which can handle insane amounts of
On Friday, 27 April 2012 at 19:40:53 UTC, F i L wrote:
vibe.d as the project name is great, but why have module
vibe.d and not simply vibe? Or, why prefix all the types with
More complicated projects/frameworks ontop of vibe which
implements it's own main is free to use vibe.all.
But I
Le 26/04/2012 22:46, Sönke Ludwig a écrit :
During the last few months, we have been working on a new
framework for general I/O and especially for building
extremely fast web apps. It combines asynchronous I/O with
core.thread's great fibers to build a convenient, blocking
API which can handle
On 4/27/12 1:42 PM, deadalnix wrote:
It is awesome. I think some part of this could be integrated into phobos
after some refactoring. I think about databases for instance, or some
http libraries.
This is an ignorant question, but why not the async IO stuff? It seems
like it could be widely
On Friday, 27 April 2012 at 20:15:05 UTC, Tove wrote:
On Friday, 27 April 2012 at 19:40:53 UTC, F i L wrote:
vibe.d as the project name is great, but why have module
vibe.d and not simply vibe? Or, why prefix all the types with
More complicated projects/frameworks ontop of vibe which
On 4/27/12 4:46 AM, Sönke Ludwig wrote:
During the last few months, we have been working on a new
framework for general I/O and especially for building
extremely fast web apps. It combines asynchronous I/O with
core.thread's great fibers to build a convenient, blocking
API which can handle
On 4/27/12 2:50 PM, Brad Anderson wrote:
On Thursday, 26 April 2012 at 20:46:41 UTC, Sönke Ludwig wrote:
During the last few months, we have been working on a new
framework for general I/O and especially for building
extremely fast web apps. It combines asynchronous I/O with
core.thread's great
On 4/28/12 8:12 AM, Ary Manzana wrote:
On 4/27/12 4:46 AM, Sönke Ludwig wrote:
During the last few months, we have been working on a new
framework for general I/O and especially for building
extremely fast web apps. It combines asynchronous I/O with
core.thread's great fibers to build a
During the last few months, we have been working on a new
framework for general I/O and especially for building
extremely fast web apps. It combines asynchronous I/O with
core.thread's great fibers to build a convenient, blocking
API which can handle insane amounts of connections due to
the low
Wow, thanks :)
Definately going to play with it.
Am 26.04.2012 23:18, schrieb ponce:
Wow, thanks :)
Definately going to play with it.
Same here, I think using vibe with nginx as reverse proxy will work great!
Looks promising.
Though I wouldn't know how to choose between Adam's web framework,
Cybershadow's code (seemed like he coded the newsreader in no time and it
works very nicely) and yours.
Any advice?
Sönke Ludwig:
See http://vibed.org/ for more information and some example
I see the code:
import vibe.d;
...
static this()
{
listenTcp(7, (conn){ conn.write(conn) });
}
Isn't it better to use this?
import vibe.all;
And in the last line is a semicolon missing?
listenTcp(7,
On 26/04/2012 21:46, Sönke Ludwig wrote:
vibe.d
This looks awesome!
Also on reddit:
http://www.reddit.com/r/programming/comments/su9la/vibed_asynchronous_io_that_doesnt_get_in_your_way/
and hacker news:
https://news.ycombinator.com/item?id=3896197
--
Robert
http://octarineparrot.com/
On Thursday, 26 April 2012 at 20:46:41 UTC, Sönke Ludwig wrote:
During the last few months, we have been working on a new
framework for general I/O and especially for building
extremely fast web apps.
Very nice, amazing job! This is like my personal plans and hopes
coming to life.
1 - 100 of 102 matches
Mail list logo
