Blog de Flap

Eli Wheaton wrote:
> I’m having a problem trying to get SQLite to work with a C++Builder6
> project.
> Does anyone have any advice on how to do this?

Hi Eli,

I am using Borland’s BCB6 with SQLite.

I have built SQLite DLL’s using both the Borland compiler, and also the
MinGW/Msys tool set. I currently use MinGW to build the DLL from CVS source,
since it is simpler to use. The current SQLite Makefile has an implib target
which will build the import library that the Borland compiler needs to link
against the DLL.

If you don’t need to build SQLite from source you can simply download the
current SQLite.DLL library from the web site
http://www.hwaci.com/sw/sqlite/download.html. You will also need the
sqlite.h header file which is included in the sqlite_source.zip file that
you can download from the same site.

To build a project that uses the DLL you will need to generate a Borland
import library. BCB6 comes with a command line tool called implib that will
do this. Simply open a command promt window, change to the directory where
the DLL is located, and run the following command (assuming that the Borland
bin directory is on your path);

implib -a sqlite.lib sqlite.dll

The -a argument is required to generate the correct symbol names in the
import library.

Now create a project that uses SQLite. The sample code at
http://www.hwaci.com/sw/sqlite/quickstart.html should work just fine for a
test. You will need to make sure the project options have the path to the
sqlite.h include file, and the path to the sqlite.lib library files set.
Build your project to generate your executable. Finally, you need to copy
the SQLite.DLL file into the same directory as your executable (or into the
Windows/System directory) since that is where Windows will look for the DLL.

You can now run your program, and it should create an SQLite database and
execute the SQL statement you give it.

Good luck.

Le plugin Google Video

Syntaxe de Wiki

Les vidéos sur Google Video ont une IDENTITÉ unique. On trouve facilement cette IDENTITÉ sur le site Google Video car elle est composée d’une série de chiffres et apparaît dans l’URL lorsque vous consultez la vidéo.

Affichage direct des vidéos

Syntaxe Wiki

{{googlevideo>small:ID_VIDEO_GOOGLE}}

{{googlevideo>large:ID_VIDEO_GOOGLE}}

Code Source

1. Créez un répertoire ’googlevideo’ dans le répertoire ‘/lib/plugins’.
2. Copiez le code suivant et collez le dans un fichier nommé syntax.php.
3. Mettez le fichier syntax.php dans le répertoire ‘googlevideo’.

http://flap.free.fr/google_video/syntaxphp.txt

http://www.subnet-calculator.com/subnet.php?net_class=A

Embarqué

http://www.routerboard.com/

http://www.mikrotik.com/

Matériel radio

http://www.wirelesslan.gr/

http://www.interprojekt.pl/

http://www.diswire.com/

http://eshop.cznet.cz/

La source

http://www.routerboard.com/sales.html

http://www.voipbuster.com/

http://www.voipstunt.com/

http://www.voipcheap.co.uk/

http://www.netappel.fr/

http://www.sipdiscount.com/

http://doulos.wordpress.com/technical-information/finarea/

http://doulos.wordpress.com/technical-information/finarea-asterisk/

Voici un massage envoyé par Thomas Lopatic, développeur du projet olsr, sur la liste de diffusion des utilisateurs. Il explique la portée de certains paramètres qui sont extrèmement intéressants…

Hi Karl,

You might want to try setting the HelloValidityTime parameter to a
higher than default value. In your case, with links there are two
mechanisms at work - (1) link detection and (2) link quality. The link
quality case is what you care for with the large window size. However,
in your configuration file you do not change the link detection
parameters. By default, every two seconds a node broadcasts a HELLO
message to announce its existence to its neighbours. The corresponding
configuration line would be “HelloInterval 2.0″. In its HELLO messages
it also says “if you do not hear a HELLO message for six seconds,
consider me dead”. The corresponding configuration line would be
“HelloValidityTime 6.0″. So, if three HELLOs in a row are lost, then the
link is considered down, irrespective of the link quality window size.

So, what this all boils down to is that we recommend setting the
“HelloValidityTime” to “HelloInterval x LinkQualityWinSize”, i.e. to use
“HelloValidityTime 120.0″ on *all* nodes in your mesh. (Remember that
setting this value on node X influences the behaviour of X’s neighbours,
i.e. if you set the validity time to 120 seconds on node X, all of X’s
neighbours will consider the link to X existent as long as there’s at
least one HELLO from X every 120 seconds.)

In this way, we guarantee that link detection will not remove a link
before link quality has had a chance to let it’s link quality decay to
the worst possible case, which is that LinkQualityWinSize x
HelloInterval packets have been lost. So, basically, what we do is, we
switch off link detection and leave it all to link quality.

So, I’d recommend adding “HelloValidityTime 120.0″ to your interface
configuration.

BTW, “HelloInterval x LinkQualityWinSize” is the default setting for
HelloValidityTime in 0.4.10, which is used if the user doesn’t specify
anything else. So for 0.4.10 your configuration will work as is.

-Thomas

OZOOD Solutions nous propose gratuitement depuis sont site http://www.ozmonitor.net/ de superviser nos sites web. Pour cela, il suffit d’aller sur leur site, de créer un compte en référençant le site à surveiller et le tour est joué.

C’est un service intéressant qui permet de remonter des alertes afin de ne pas passer à cotés de problèmes d’accès…

C’est pas une grande information, ok, mais c’est la première…

Ce site est hébergé chez ovh sur un 90plan (le même que www.mynetmemo.com).

Peut-être bientôt une informations me concernant ici