CustomAction

[Glenn Steen]

On 31/07/07, UxBoD <uxbod at splatnix.net> wrote:
> Question on efficiency?
>
> For writing to a database when the CustomAction is used I have in mind three different methods :-
>
> 1) Open SQL connection, insert, close connection
High overhead, safe, easy to implement.

> 2) Connect to a file socket, write data, and then a seperate daemon would read from the socket, manipulate data and write to SQL
Low (even very low) overhead, not as easy to implement as #1, "locked"
to one server (for the daemon part, not necessarily the SQL bit the
daemon does:-).

> 3) As per 3 but use a TCP socket direct to daemon
Marginally (well:) higher overhead than #2, no big difference in
implementation "hardness", not locked to one server for the daemon
part.

> Which do you reckon would be the quickest? Off loading to seperate daemon would hopefully not impact on MS performance then.
>
Quickest in what way? To implement: #1, performance-wise? Likely #2,
but depending on a lot of factors, #3 could well be the way to go.

(snip, just for you  Kai and Evil Bunny;-)

Cheers
-- 
-- Glenn
email: glenn < dot > steen < at > gmail < dot > com
work: glenn < dot > steen < at > ap1 < dot > se