Hi
Thinking more about this, I'd have to say DBIx::IPC still seems a good
choice.
The point is that IPC is an important part, but it's no more than an
implementation detail, in that it's not the whole point of the module.
In other words, you're not using dbs just to use ipc!
You're using ipc in order to use dbs. The dbs are definitely the point
of the exercise.
On 26/07/13 09:30, [email protected] wrote:
Hi!
The reason to choose this namespace was because i didn't found any which
connects IPC (queues, shared memory etc) and database layer in the same time.
The database is only a storage for all data (thanks to this communication
between servers is easy, it keeps state (even if clients are inactive) but
that's all. It is not extension for DBI
This is more some extension to IPC.
But anyway i need about two weeks to rewrite this group of modules. I will send
then link to github here. So then, after looking at it, you or someone from the
list can have idea where it fits the best.
Regards!
Pawel
------Oryginalna wiadomość------
Od: Ron Savage
Do: [email protected]
Do: modules-perl.org
Temat: Re: Module submission IPCdb
Wysłano: 26 lip 2013 00:51
Hi Paweł
Is there any particular reason you've used a top-level namespace?
I'd feel much happier if you called your module DBIx::IPC.
If you do a CPAN search on DBIx you'll see a whole set of modules under
DBIx and I'd say that's where your module belongs.
--
Ron Savage
http://savage.net.au/
Ph: 0421 920 622
