2014-04-28
2014-04-28. Open Source › Open Source libraries
Mustache is a well-known
logic-less template engine.
There is plenty of Open Source implementations around (including in JavaScript,
which can be very convenient for AJAX applications on client side, for
instance).
For mORMot, we created the first pure Delphi implementation of it,
with a perfect integration with other bricks of the framework.
In this first part of this series of blog articles, we will introduce the
Mustache design.
You can download this documentation
as one single pdf file.
2014-04-18
2014-04-18. Open Source › mORMot Framework
We have just released a set of slides introducing ORM, SOA, REST, JSON, MVC, MVVM, SOLID, Mocks/Stubs, Domain-Driven Design concepts with Delphi, and showing some sample code using our Open Source mORMot framework. You can follow the public link on Google Drive! This is a great opportunity to […]
2014-04-07
2014-04-07. Open Source › mORMot Framework
As we already
stated, we finished the first step of integration of the
SpiderMonkey engine to our mORMot framework.
Version 1.8.5 of the library is already integrated, and latest official
revision will be soon merged,
thanks to mpv's great contribution.
It can be seen as stable, since it is already used on production site to serve more than
1,000,000 requests per day.
You can now easily uses JavaScript on both client and server side.
On server side, mORMot's implementation offers an unique concept, i.e.
true multi-threading,
which is IMHO a huge enhancement when compared to the regular node.js mono-threaded implementation,
and its callback hell.
In fact, node.js official marketing states its non-blocking scheme is
a plus. It allows to define a HTTP server in a few lines, but huge server
applications need JavaScript experts not to sink into a state a
disgrace.
2014-02-28
2014-02-28. Open Source
After more than 5 years of opening some huge part of Delphi code base, just my two cents.
Free software means free as a bird.
In practice, most Open Source "consumers" focus on free as a free
beer...
This is a reality, especially for "niche" projects like developing libraries
for Delphi.
Here are some thoughts from my little experiment with mORMot.
If you ask what Open Source for libraries mean, it may help you!
2014-01-04
2014-01-04. Open Source › mORMot Framework
One year ago, we already made a quick presentation of
Domain-Driven Design, in the context of our mORMot
framework.
After one year of real-world application of those patterns, it is now time to
give more light to DDD.
Let's continue with part 4, which will define Domain-Driven Design as could be implemented with our Synopse mORMot framework
2014-01-04. Open Source › mORMot Framework
One year ago, we already made a quick presentation of
Domain-Driven Design, in the context of our mORMot
framework.
After one year of real-world application of those patterns, it is now time to
give more light to DDD.
Let's continue with part 3, which will define Domain-Driven Design patterns and principles - this will be the main article of the whole serie!
2014-01-04. Open Source › mORMot Framework
One year ago, we already made a quick presentation of
Domain-Driven Design, in the context of our mORMot
framework.
After one year of real-world application of those patterns, it is now time to
give more light to DDD.
Let's continue with part 2, which will define Domain-Driven Design high-level model principles.
2014-01-04. Open Source › mORMot Framework
One year ago, we already made a quick presentation of
Domain-Driven Design, in the context of our mORMot
framework.
After one year of real-world application of those patterns, and a training made
by a great French software designer named Jérémie Grodziski, it is now time to give more
light to DDD.
Let's start with part 1, which will be a general introduction to Domain-Driven Design, trying to state how it may be interesting (or not) for your projects.
2013-09-10
2013-09-10. Open Source › mORMot Framework
We tried to make mORMot at the same time fast and safe, and able to
scale with the best possible performance on the hardware it runs on.
Multi-threading is the key to better usage of modern multi-core CPUs, and also
client responsiveness.
As a result, on the Server side, our framework was designed to be thread-safe.
On typical production use, the mORMot HTTP server will run on its
own optimized thread pool, then call the TSQLRestServer.URI
method. This method is therefore expected to be thread-safe, e.g. from the
TSQLHttpServer. Request method. Thanks to the RESTful approach of
our framework, this method is the only one which is expected to be thread-safe,
since it is the single entry point of the whole server. This KISS design ensure
better test coverage.
Let us see now how this works, and publish some benchmarks to test how efficient it has been implemented.
2013-07-24
2013-07-24. Pascal Programming
I'm currently fighting against out of memory errors on an heavy-loaded Java server.
If only it had been implemented in Delphi and mORMot!
But at this time, the mORMot was still in its burrow. 
Copy-On-Write and a good heap manager can do wonders of stability.
Here are some thoughts about Garbage Collector, and how to temper
their limitations.
They may apply to both the JVM and the .Net runtime, by the way.
2013-07-04
2013-07-04. Open Source › mORMot Framework
In mORmot applications, all the client communication is executed by
default in the current thread, i.e. the main thread for a typical GUI
application.
This may become an issue in some reported
environments.
Since all communication is performed in blocking mode, if the
remote request takes long to process (due to a bad/slow network, or a long
server-side action), the application may become unresponsive, from the end-user
experience.
Even Windows may be complaining about a "non responsive application",
and may propose to kill the process, which is far away from an expected
behavior.
In order to properly interacts with the user, a OnIdle property
has been defined in TSQLRestClientURI, and will change the way
communication is handled.
If a callback event is defined, all client communication will be processed in a
background thread, and the current thread (probably the main UI thread) will
wait for the request to be performed in the background, running the
OnIdle callback in loop in the while.
2013-05-19
2013-05-19. Pascal Programming
One quick Sunday post, from a comment I wrote in a blog article.
I'm always wondering why a lot of programmers tend to implicitly assume that "the shorter source code, the better".
It is true when it means that with proper code refactoring, making small
objects with dedicated methods, the code of your methods will be smaller.
It is true when you do not like to write as a "Copy & Paste" coder, without
searching to put common code in shared places.
But is it true at the language level?
I mean, is it just because your ARC or GC model allow you not to manage the
object memory, that it is always better?
Just some ideas...
2013-03-26
2013-03-26. Pascal Programming
On the Embarcadero
forums, some user did have a perfectly sane reaction, about a non obvious
integer type cast like Int64Var := Int32Var*Int32Var, which may
overflow.
We've got to stop becoming, as one poster put it, "human pre-compilers" for Delphi.
The compiler ought to have the common sense to not need the programmer to cast the two integer values.
I respectfully think just the opposite.
;)
Such a type cast is part of the language grammar.
If you know the grammar, you will know how it will be compiled.
To be honest, you have the same in all languages, with more or less range
checking, optimization, and implicit conversion.
This is why I like Delphi: it can be mastered by any programmers, whereas truly
mastering Java or .Net needs a genius.
Delphi is just... human...
2013-03-25
2013-03-25. Open Source › SynProject documentation and versioning
We have uploaded an updatetd compiled version of our Open Source SynProject tool in SynProject.zip. Synopse SynProject is an open source application for code source versioning and automated documentation of software projects. Licensed under a GPL license. Main feature is a new (better-looking?) […]
2013-02-03
2013-02-03. Open Source › mORMot Framework
Our framework features an integrated logging class, ready to be enabled for support and statistics.
For debugging purposes, it could be very handy to output the logging content
to a console window.
It enables interactive debugging of a Client-Server process, for instance: you
can interact with the Client, then look in real time at the server console
window, and inspect which requests are processed, without the need to open the
log file.
Depending on the events, colors will be used to write the corresponding information. Errors will be displayed as light red, for instance.
2013-01-27
2013-01-27. Open Source › mORMot Framework
A new mORMot user notified on our forum that he just made a short video, about authentication and security with our framework, from the perspective of an AJAX Client. Many thanks for sharing your experiences! This video illustrate how RESTful authentication is implemented by mORMot. It compares also […]
2013-01-05
2013-01-05. Open Source › mORMot Framework
Implementing Domain-Driven-Design (DDD) is one goal of our mORMot framework.
We already presented this particular n-Tier architecture.
It is now time to enter deeper into the material, provide some definition
and reference.
You can also search the web for reference, or look at the official web site.
A general
presentation of the corresponding concepts, in the .NET world, was used as
reference of this blog entry.
Stay tuned, and ride the mORMot!
2012-12-31
2012-12-31. Open Source › mORMot Framework
Even if mORMot will be more easily used in a project designed from scratch, it fits very well the purpose of evolving any existing Delphi project, or even creating the server side part of an AJAX application.
One benefit of such a framework is to facilitate the transition from a Client-Server architecture to a N-Tier layered pattern.
2012-11-20
2012-11-20. Open Source › mORMot Framework
By default, the hash of the user password is stored safely on the server side. This may be an issue for corporate applications, since a new user name / password pair is to be defined by each client, which may be annoying.
Since revision 1.18 of the framework, mORMot is able to use Windows Authentication to identify any user. That is, the user does not need to enter any name nor password, but her/his Windows credentials, as entered at Windows session startup, will be used.
Thanks a lot Chaa for making public your
code proposal!
Open Source is so great sometimes!
Keep the good work!
2012-10-18
2012-10-18. Pascal Programming
A very interesting comment by mpv in our forum highlighted some points about potential interface (ab)use:
IMHO: Idea is good, but "the devil is in the details". To use mocking I must use interfaces. When I use interfaces I lost control on code, because I don't see implementation. Debugging an optimization became very hard. Especially if a beginner developer read something like GOF (Gang Of Four) and wherever necessary and where not use design templates like Visitor, Decorator and so on, and in debugging I don't understand at all what class actually implement passed interface. As for me, this is a biggest problem for .NET framework - developers use interfaces, don't look on implementation (and often don't have it in sources at all), do not learn by reading someone else's code and therefore produce monkey-code. This is only IMHO...
Could sounds rude, and like a trolling subject, but I perfectly understand
this point of view.
Introducing stubs and mocks
in mORMot was not the open door to all problems.. but,on the contrary,
to help write robust, efficient, and maintainable code.
It does not mean that using interfaces and C#/Java is the root of all evils and
code inefficiency, but that it may lead into problems.
« previous entries - page 3 of 5 - next entries »
