description: When using local fdb files, we meet two questions:
1)developers always expect their application to be very neat in destribution ,especially for loacal databases. In this case,embeded firebird is a perfect choice.
2)Yet local database software often need concurrent multiple connections. In this case, we have to use FB server.

What about mix the two feature into one product? Sybase's SQLAnywhere perhaps do it. When an application starts to access a db, SQLAnywhere's client library will automatically starts a server process. when the server determined no clients are connected, it will automatically close itself. This is a very good feature for local(but multi user) database application, since the server engine need not to be installed as service and the whole application can be very portable, simply pack the server executables along with the applicaiton and the system will work. This will make the DB Server really portable,or embedable. I wish firebird will do the same job. What's more cool is, that I've learned there's certain techniques,allows a process to be started based from an in-memory image, not neccecarilly from a hard disk exe file. So it's possible that the embeded server could start a backgroud server process to serve multiple connections, and the server executalbe image can be attached as a resource with embeded FireBird dll. I think this is really cool if it's implemented in future embeded edition of firebird, and we can use embeded firebird in multi-process server side environments.

=>

When using local fdb files, we meet two questions:
1)developers always expect their application to be very neat in destribution ,especially for loacal databases. In this case,embeded firebird is a perfect choice.
2)Yet local database software often need concurrent multiple connections. In this case, we have to use FB server.

What about mix the two feature into one product? Sybase's SQLAnywhere perhaps do it. When an application starts to access a db, SQLAnywhere's client library will automatically starts a server process. when the server determined no clients are connected, it will automatically close itself. This is a very good feature for local(but multi user) database application, since the server engine need not to be installed as service and the whole application can be very portable, simply pack the server executables along with the applicaiton and the system will work. This will make the DB Server really portable,or embedable. I wish firebird will do the same job. What's more cool is, that I've learned there's certain techniques,allows a process to be started based from an in-memory image, not neccecarilly from a hard disk exe file. So it's possible that the embeded server could start a backgroud server process to serve multiple connections, and the server executalbe image can be attached as a resource with embeded FireBird dll. I think this is really cool if it's implemented in future embeded edition of firebird, and we can use embeded firebird in multi-process server side applications.

description: When using local fdb files, we meet two questions:
1)developers always expect their application to be very neat in destribution ,especially for loacal databases. In this case,embeded firebird is a perfect choice.
2)Yet local database software often need concurrent multiple connections. In this case, we have to use FB server.

What about mix the two feature into one product? Sybase's SQLAnywhere perhaps do it. When an application starts to access a db, SQLAnywhere's client library will automatically starts a server process. when the server determined no clients are connected, it will automatically close itself. This is a very good feature for local(but multi user) database application, since the server engine need not to be installed as service and the whole application can be very portable, simply pack the server executables along with the applicaiton and the system will work. This will make the DB Server really portable,or embedable. I wish firebird will do the same job. What's more cool is, that I've learned there's certain techniques,allows a process to be started based from an in-memory image, not neccecarilly from a hard disk exe file. So it's possible that the embeded server could start a backgroud server process to serve multiple connections, and the server executalbe image can be attached as a resource with embeded FireBird dll. I think this is really cool if it's implemented in future embeded edition of firebird, and we can use embeded firebird in multi-process server side applications.

=>

When using local fdb files, we meet two questions:
1)developers always expect their application to be very neat in destribution ,especially for loacal databases. In this case,embeded firebird is a perfect choice.
2)Yet local database software often need concurrent multiple connections. In this case, we have to use FB server.

What about mix the two feature into one product? Sybase's SQLAnywhere perhaps do it. When an application starts to access a db, SQLAnywhere's client library will automatically starts a server process. when the server determined no clients are connected, it will automatically close itself. This is a very good feature for local(but multi user) database application, since the server engine need not to be installed as service and the whole application can be very portable, simply pack the server executables along with the applicaiton and the system will work. This will make the DB Server really portable,or embedable. I wish firebird will do the same job. What's more cool is, that I've learned there's certain techniques,allows a process to be started based from an in-memory image, not neccecarilly from a hard disk exe file. So it's possible that the embeded server could start a backgroud server process to serve multiple connections, and the server executalbe image can be attached as a resource with embeded FireBird dll. I think this is really cool if it's implemented in future embeded edition of firebird, and at the time we can develope multi-process server side applications based on embeded FireBird, or deliver really portable and professional local db software with it.

description: When using local fdb files, we meet two questions:
1)developers always expect their application to be very neat in destribution ,especially for loacal databases. In this case,embeded firebird is a perfect choice.
2)Yet local database software often need concurrent multiple connections. In this case, we have to use FB server.

What about mix the two feature into one product? Sybase's SQLAnywhere perhaps do it. When an application starts to access a db, SQLAnywhere's client library will automatically starts a server process. when the server determined no clients are connected, it will automatically close itself. This is a very good feature for local(but multi user) database application, since the server engine need not to be installed as service and the whole application can be very portable, simply pack the server executables along with the applicaiton and the system will work. This will make the DB Server really portable,or embedable. I wish firebird will do the same job. What's more cool is, that I've learned there's certain techniques,allows a process to be started based from an in-memory image, not neccecarilly from a hard disk exe file. So it's possible that the embeded server could start a backgroud server process to serve multiple connections, and the server executalbe image can be attached as a resource with embeded FireBird dll. I think this is really cool if it's implemented in future embeded edition of firebird, and at the time we can develope multi-process server side applications based on embeded FireBird, or deliver really portable and professional local db software with it.

=>

When using local fdb files, we meet two questions:
1)developers always expect their application to be very neat in destribution ,especially for loacal databases. In this case,embeded firebird is a perfect choice.
2)Yet local database software often need concurrent multiple connections. In this case, we have to use FB server.

What about mix the two feature into one product? Sybase's SQLAnywhere perhaps do it. When an application starts to access a db, SQLAnywhere's client library will automatically starts a server process. when the server determined no clients are connected, it will automatically close itself. This is a very good feature for local(but multi user) database application, since the server engine need not to be installed as service and the whole application can be very portable, simply pack the server executables along with the applicaiton and the system will work. This will make the DB Server really portable,or embedable. I wish firebird will do the same job. What's more cool is, that I've learned there's certain techniques,allows a process to be started based from an in-memory image, not necessarilly from a hard disk exe file. So it's possible that the embeded server could start a backgroud server process to serve multiple connections, and the server executalbe image can be attached as a resource with embeded FireBird dll. I think this is really cool if it's implemented in future embeded edition of firebird, and at the time we can develope multi-process server side applications based on embeded FireBird, or deliver really portable and professional local db software with it.

description: When using local fdb files, we meet two questions:
1)developers always expect their application to be very neat in destribution ,especially for loacal databases. In this case,embeded firebird is a perfect choice.
2)Yet local database software often need concurrent multiple connections. In this case, we have to use FB server.

What about mix the two feature into one product? Sybase's SQLAnywhere perhaps do it. When an application starts to access a db, SQLAnywhere's client library will automatically starts a server process. when the server determined no clients are connected, it will automatically close itself. This is a very good feature for local(but multi user) database application, since the server engine need not to be installed as service and the whole application can be very portable, simply pack the server executables along with the applicaiton and the system will work. This will make the DB Server really portable,or embedable. I wish firebird will do the same job. What's more cool is, that I've learned there's certain techniques,allows a process to be started based from an in-memory image, not necessarilly from a hard disk exe file. So it's possible that the embeded server could start a backgroud server process to serve multiple connections, and the server executalbe image can be attached as a resource with embeded FireBird dll. I think this is really cool if it's implemented in future embeded edition of firebird, and at the time we can develope multi-process server side applications based on embeded FireBird, or deliver really portable and professional local db software with it.

=>

When using local fdb files, we meet two questions:
1)developers always expect their application to be very neat in destribution ,especially for loacal databases. In this case,embeded firebird is a perfect choice.
2)Yet local database software often need concurrent multiple connections. In this case, we have to use FB server.

What about mix the two feature into one product? Sybase's SQLAnywhere perhaps do it. When an application starts to access a db, SQLAnywhere's client library will automatically starts a server process. when the server determined no clients are connected, it will automatically close itself. This is a very good feature for local(but multi user) database application, since the server engine need not to be installed as service and the whole application can be very portable, simply pack the server executables along with the applicaiton and the system will work. This will make the DB Server really portable,or embedable. I wish firebird will do the same job. What's more cool is, that I've learned there's certain techniques,allows a process to be started based from an in-memory image, not necessarilly from a hard disk exe file. So it's possible that the embeded server could start a backgroud server process to serve multiple connections, and the server executalbe image can be attached as a resource with embeded FireBird dll. I think this is really cool if it's implemented in future embeded edition of firebird, and at the time we can develope multi-process server side applications based on embeded FireBird, or deliver really portable and professional local db software with it.
And, the feature I suggested should be an addition, not a replacement to the current embeded engine, because for many cases, the exclusive access to a fdb file in current embeded firebird engine is just good. The multi-user mode should be an extra mode of embeded engine.

description: When using local fdb files, we meet two questions:
1)developers always expect their application to be very neat in destribution ,especially for loacal databases. In this case,embeded firebird is a perfect choice.
2)Yet local database software often need concurrent multiple connections. In this case, we have to use FB server.

What about mix the two feature into one product? Sybase's SQLAnywhere perhaps do it. When an application starts to access a db, SQLAnywhere's client library will automatically starts a server process. when the server determined no clients are connected, it will automatically close itself. This is a very good feature for local(but multi user) database application, since the server engine need not to be installed as service and the whole application can be very portable, simply pack the server executables along with the applicaiton and the system will work. This will make the DB Server really portable,or embedable. I wish firebird will do the same job. What's more cool is, that I've learned there's certain techniques,allows a process to be started based from an in-memory image, not necessarilly from a hard disk exe file. So it's possible that the embeded server could start a backgroud server process to serve multiple connections, and the server executalbe image can be attached as a resource with embeded FireBird dll. I think this is really cool if it's implemented in future embeded edition of firebird, and at the time we can develope multi-process server side applications based on embeded FireBird, or deliver really portable and professional local db software with it.
And, the feature I suggested should be an addition, not a replacement to the current embeded engine, because for many cases, the exclusive access to a fdb file in current embeded firebird engine is just good. The multi-user mode should be an extra mode of embeded engine.

=>

When using local fdb files, we meet two questions:
1)developers always expect their application to be very neat in destribution ,especially for loacal databases. In this case,embeded firebird is a perfect choice.
2)Yet local database software often need concurrent multiple connections. In this case, we have to use FB server.

What about mix the two feature into one product? Sybase's SQLAnywhere perhaps do it. When an application starts to access a db, SQLAnywhere's client library will automatically starts a server process. when the server determined no clients are connected, it will automatically close itself. This is a very good feature for local(but multi user) database application, since the server engine need not to be installed as service and the whole application can be very portable, simply pack the server executables along with the applicaiton and the system will work. This will make the DB Server really portable,or embedable. I wish firebird will do the same job. What's more cool is, that I've learned there's certain techniques,allows a process to be started based from an in-memory image, not necessarilly from a hard disk exe file. So it's possible that the embeded server could start a backgroud server process to serve multiple connections, and the server executalbe image can be attached as a resource with embeded FireBird dll. I think this is really cool if it's implemented in future embeded edition of firebird, and at the time we can develope multi-process server side applications based on embeded FireBird, or deliver really portable and professional local db software with it.
And, the feature I suggested should be an addition, not a replacement to the current embeded engine's manner, because for many cases, the exclusive access to a fdb file in current embeded firebird engine is just good. The multi-user mode should be an extra mode of embeded engine.

description: When using local fdb files, we meet two questions:
1)developers always expect their application to be very neat in destribution ,especially for loacal databases. In this case,embeded firebird is a perfect choice.
2)Yet local database software often need concurrent multiple connections. In this case, we have to use FB server.

What about mix the two feature into one product? Sybase's SQLAnywhere perhaps do it. When an application starts to access a db, SQLAnywhere's client library will automatically starts a server process. when the server determined no clients are connected, it will automatically close itself. This is a very good feature for local(but multi user) database application, since the server engine need not to be installed as service and the whole application can be very portable, simply pack the server executables along with the applicaiton and the system will work. This will make the DB Server really portable,or embedable. I wish firebird will do the same job. What's more cool is, that I've learned there's certain techniques,allows a process to be started based from an in-memory image, not necessarilly from a hard disk exe file. So it's possible that the embeded server could start a backgroud server process to serve multiple connections, and the server executalbe image can be attached as a resource with embeded FireBird dll. I think this is really cool if it's implemented in future embeded edition of firebird, and at the time we can develope multi-process server side applications based on embeded FireBird, or deliver really portable and professional local db software with it.
And, the feature I suggested should be an addition, not a replacement to the current embeded engine's manner, because for many cases, the exclusive access to a fdb file in current embeded firebird engine is just good. The multi-user mode should be an extra mode of embeded engine.

=>

When using local fdb files, we meet two questions:
1)developers always expect their application to be very neat in destribution ,especially for loacal databases. In this case,embeded firebird is a perfect choice.
2)Yet local database software often need concurrent multiple connections. In this case, we have to use FB server.

What about mix the two feature into one product? Sybase's SQLAnywhere perhaps do it\. When an application starts to access a db, SQLAnywhere's client library will automatically starts a server process\. when the server determined no clients are connected, it will automatically close itself\. This is a very good feature for local\(but multi user\) database application, since the server engine need not to be installed as service and the whole application can be very portable, simply pack the server executables along with the applicaiton and the system will work\. This will make the DB Server really portable,or embedable\. I wish firebird will do the same job\. What's more cool is, that I've learned there's certain techniques,allows a process to be started based from an in\-memory image, not necessarilly from a hard disk exe file\. So it's possible that the embeded server could start a backgroud server process to serve multiple connections, and the server executalbe image can be attached as a resource with embeded FireBird dll\. I think this is really cool if it's implemented in future embeded edition of firebird, and at the time we can develope multi\-process server side applications based on embeded FireBird, or deliver really  portable and professional local db software with it\.
And, the feature I suggested should be an addition, not a replacement to the current embeded engine's manner, because for many cases, the exclusive access to a fdb file in current  embeded engine is just good with its best performance\. The multi\-user mode should be an extra mode of the engine\. 

description: When using local fdb files, we meet two questions:
1)developers always expect their application to be very neat in destribution ,especially for loacal databases. In this case,embeded firebird is a perfect choice.
2)Yet local database software often need concurrent multiple connections. In this case, we have to use FB server.

What about mix the two feature into one product? Sybase's SQLAnywhere perhaps do it\. When an application starts to access a db, SQLAnywhere's client library will automatically starts a server process\. when the server determined no clients are connected, it will automatically close itself\. This is a very good feature for local\(but multi user\) database application, since the server engine need not to be installed as service and the whole application can be very portable, simply pack the server executables along with the applicaiton and the system will work\. This will make the DB Server really portable,or embedable\. I wish firebird will do the same job\. What's more cool is, that I've learned there's certain techniques,allows a process to be started based from an in\-memory image, not necessarilly from a hard disk exe file\. So it's possible that the embeded server could start a backgroud server process to serve multiple connections, and the server executalbe image can be attached as a resource with embeded FireBird dll\. I think this is really cool if it's implemented in future embeded edition of firebird, and at the time we can develope multi\-process server side applications based on embeded FireBird, or deliver really  portable and professional local db software with it\.
And, the feature I suggested should be an addition, not a replacement to the current embeded engine's manner, because for many cases, the exclusive access to a fdb file in current  embeded engine is just good with its best performance\. The multi\-user mode should be an extra mode of the engine\. 

=>

When using local fdb files, we meet two questions:
1)developers always expect their application to be very neat in destribution ,especially for loacal databases. In this case,embeded firebird is a perfect choice.
2)Yet local database software often need concurrent multiple connections. In this case, we have to use FB server.

What about mix the two feature into one engine? Sybase's SQLAnywhere perhaps do it\. When an application starts to access a db, SQLAnywhere's client library will automatically starts a server process\. when the server determined no clients are connected, it will automatically close itself\. This is a very good feature for local\(but multi user\) database application, since the server engine need not to be installed as service and the whole application can be very portable, simply pack the server executables along with the applicaiton and the system will work\. This will make the DB Server really portable,or embedable\. I wish firebird will do the same job\. What's more cool is, that I've learned there's certain techniques,allows a process to be started based from an in\-memory image, not necessarilly from a hard disk exe file\. So it's possible that the embeded server could start a backgroud server process to serve multiple connections, and the server executalbe image can be attached as a resource with embeded FireBird dll\. I think this is really cool if it's implemented in future embeded edition of firebird, and at the time we can develope multi\-process server side applications based on embeded FireBird, or deliver really  portable and professional local db software with it\.
And, the feature I suggested should be an addition, not a replacement to the current embeded engine's manner, because for many cases, the exclusive access to a fdb file in current  embeded engine is just good with its best performance\. The multi\-user mode should be an extra mode of the engine\. 

description: When using local fdb files, we meet two questions:
1)developers always expect their application to be very neat in destribution ,especially for loacal databases. In this case,embeded firebird is a perfect choice.
2)Yet local database software often need concurrent multiple connections. In this case, we have to use FB server.

What about mix the two feature into one engine? Sybase's SQLAnywhere perhaps do it\. When an application starts to access a db, SQLAnywhere's client library will automatically starts a server process\. when the server determined no clients are connected, it will automatically close itself\. This is a very good feature for local\(but multi user\) database application, since the server engine need not to be installed as service and the whole application can be very portable, simply pack the server executables along with the applicaiton and the system will work\. This will make the DB Server really portable,or embedable\. I wish firebird will do the same job\. What's more cool is, that I've learned there's certain techniques,allows a process to be started based from an in\-memory image, not necessarilly from a hard disk exe file\. So it's possible that the embeded server could start a backgroud server process to serve multiple connections, and the server executalbe image can be attached as a resource with embeded FireBird dll\. I think this is really cool if it's implemented in future embeded edition of firebird, and at the time we can develope multi\-process server side applications based on embeded FireBird, or deliver really  portable and professional local db software with it\.
And, the feature I suggested should be an addition, not a replacement to the current embeded engine's manner, because for many cases, the exclusive access to a fdb file in current  embeded engine is just good with its best performance\. The multi\-user mode should be an extra mode of the engine\. 

=>

When using local fdb files, we meet two questions:
1)developers always expect their application to be very neat in destribution ,especially for loacal databases. In this case,embeded firebird is a perfect choice.
2)Yet local database software often need concurrent multiple connections. In this case, we have to use FB server.

What about mixing the two feature into one engine? Sybase's SQLAnywhere perhaps do it\. When an application starts to access a db, SQLAnywhere's client library will automatically starts a server process\. when the server determined no clients are connected, it will automatically close itself\. This is a very good feature for local\(but multi user\) database application, since the server engine need not to be installed as service and the whole application can be very portable, simply pack the server executables along with the applicaiton and the system will work\. This will make the DB Server really portable,or embedable\. I wish firebird will do the same job\. What's more cool is, that I've learned there's certain techniques,allows a process to be started based from an in\-memory image, not necessarilly from a hard disk exe file\. So it's possible that the embeded server could start a backgroud server process to serve multiple connections, and the server executalbe image can be attached as a resource with embeded FireBird dll\. I think this is really cool if it's implemented in future embeded edition of firebird, and at the time we can develope multi\-process server side applications based on embeded FireBird, or deliver really  portable and professional local db software with it\.
And, the feature I suggested should be an addition, not a replacement to the current embeded engine's manner, because for many cases, the exclusive access to a fdb file in current  embeded engine is just good with its best performance\. The multi\-user mode should be an extra mode of the engine\. 

description: When using local fdb files, we meet two questions:
1)developers always expect their application to be very neat in destribution ,especially for loacal databases. In this case,embeded firebird is a perfect choice.
2)Yet local database software often need concurrent multiple connections. In this case, we have to use FB server.

What about mixing the two feature into one engine? Sybase's SQLAnywhere perhaps do it\. When an application starts to access a db, SQLAnywhere's client library will automatically starts a server process\. when the server determined no clients are connected, it will automatically close itself\. This is a very good feature for local\(but multi user\) database application, since the server engine need not to be installed as service and the whole application can be very portable, simply pack the server executables along with the applicaiton and the system will work\. This will make the DB Server really portable,or embedable\. I wish firebird will do the same job\. What's more cool is, that I've learned there's certain techniques,allows a process to be started based from an in\-memory image, not necessarilly from a hard disk exe file\. So it's possible that the embeded server could start a backgroud server process to serve multiple connections, and the server executalbe image can be attached as a resource with embeded FireBird dll\. I think this is really cool if it's implemented in future embeded edition of firebird, and at the time we can develope multi\-process server side applications based on embeded FireBird, or deliver really  portable and professional local db software with it\.
And, the feature I suggested should be an addition, not a replacement to the current embeded engine's manner, because for many cases, the exclusive access to a fdb file in current  embeded engine is just good with its best performance\. The multi\-user mode should be an extra mode of the engine\. 

=>

When using local fdb files, we meet two questions:
1)developers always expect their application to be very neat in destribution ,especially for loacal databases. In this case,embeded firebird is a perfect choice.
2)Yet local database software often need concurrent multiple connections. In this case, we have to use FB server.

What about mixing the two feature into one engine? Sybase's SQLAnywhere perhaps do it\. When an application starts to access a db, SQLAnywhere's client library will automatically starts a server process\. when the server determined no clients are connected, it will automatically close itself\. This is a very good feature for local\(but multi user\) database application, since the server engine need not to be installed as service and the whole application can be very portable, simply pack the server executables along with the applicaiton and the system will work\. This will make the DB Server really portable,or embedable\. I wish firebird will do the same job\. What's more cool is, that I've learned there's certain techniques,allows a process to be started based from an in\-memory image, not necessarilly from a hard disk exe file\. So it's possible that the embeded server could start a backgroud server process to serve multiple connections, and the server executalbe image can be attached as a resource with embeded FireBird dll\. I think this is really cool if it's implemented in future embeded edition of firebird, and at the time we can develope multi\-process server side applications based on embeded FireBird, or deliver really  portable and professional local db software with it\.
And, the feature I suggested should be an addition, not a replacement to the current embeded engine's manner, because for many cases, the exclusive access to a fdb file in current  embeded engine is just good with its best performance\. The multi\-user mode should be an additional mode of the engine\. 

Workflow: jira [ 11431 ] => Firebird [ 15456 ]

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

Fix Version: 2.5 Beta 2 [ 10300 ]

status: Resolved [ 5 ] => Closed [ 6 ]

QA Status: No test

status: Closed [ 6 ] => Closed [ 6 ]

QA Status: No test => Cannot be tested