anyway, you think synchronizing access would be the solution?

----- Original Message ----- 
From: "pablosantosluac" <[EMAIL PROTECTED]>
To: "For users and developers of the Firebird .NET providers" 
<firebird-net-provider@lists.sourceforge.net>
Sent: Monday, December 18, 2006 1:48 PM
Subject: Re: [Firebird-net-provider] Firebird 2.0 Embedded on Linux


> Ok, problem then is thread safety. This was exactly the problem I had on
> Linux.
>
> Is there a way to solve it apart from synchronizing calls? I guess only 
> one
> DB operation could be active at a time...
>
> ----- Original Message ----- 
> From: "Helen Borrie" <[EMAIL PROTECTED]>
> To: "For users and developers of the Firebird .NET providers"
> <firebird-net-provider@lists.sourceforge.net>
> Sent: Monday, December 18, 2006 3:29 AM
> Subject: Re: [Firebird-net-provider] Firebird 2.0 Embedded on Linux
>
>
>> At 09:31 AM 18/12/2006, you wrote:
>>>well, I actually never got it to run, it crashed due to threading
>>>problems... and I don't even know about 2.0
>>>
>>>Hello:
>>> > Well, I regularly ask the same question but... is there any progress 
>>> > on
>>> > Firebird/Mono Embedded on Linux?
>>>And what the problems of the embedded suppoer on linux ??
>>
>> There seems to be a high level of confusion about "embedded on
>> Linux", so I'm sticking my oar in here.  There is only one way to
>> build an embedded app on Linux and that's by using Classic and the
>> libfbembed.so client, i.e. Classic's original direct-connect
>> mechanism.  It *does* require the presence of the security database
>> and authentication at login and it does not use a network method for
>> the connection.  libfbembed.so is NOT thread-safe.  It presents the
>> same API but, as to whether there is a Mono data access layer for
>> Firebird that's equivalent to the Windows .net providers, Carlos
>> could best comment.
>>
>> Embedded on Windows is a different thing altogether.  For one thing,
>> it uses the "Windows local" network emulator (IPServer) for the
>> connection.  For another, it is a single instance of
>> *Superserver*.  Of course, as you know, it bypasses the security
>> database altogether and doesn't authenticate the user
>> connection.  And it uses Windows API function calls.
>>
>> Helen
>>
>>
>>
>>
>> -------------------------------------------------------------------------
>> Take Surveys. Earn Cash. Influence the Future of IT
>> Join SourceForge.net's Techsay panel and you'll get the chance to share
>> your
>> opinions on IT & business topics through brief surveys - and earn cash
>> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>> _______________________________________________
>> Firebird-net-provider mailing list
>> Firebird-net-provider@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share 
> your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Firebird-net-provider mailing list
> Firebird-net-provider@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/firebird-net-provider 


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Firebird-net-provider mailing list
Firebird-net-provider@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/firebird-net-provider

Reply via email to