On Jan 23, 2:11 am, NTMS <[email protected]> wrote:
> Hi Jason,
>
> First of all let me thank you for your kind respons.
>
> To be frankly we are trying to get a kind of product that allows us
> to:
> + Create Online Report in Real-Time
> + Create a "Rauters Endex" like Endex\ that can be updated 'n every
> secon/min
I think MV.Net would do you fine for everything except the real time
stuff, where you want to use message queues.
MV.Net might still help you get the data for real-time but the best
way to do that is to use a jBC file trigger in an appropriate place
(something that says "When this file is written to, it means the data
is ready to feed"). When the trigger fires, assemble the data you need
in the most efficient way possible, and if your server is Windows use
CALLdotNet (after cursing that this has lower case in it) and place
the data directly on to a Microsoft Message Queue. If your server is
not Windows, the you could call Java code and place it on Rendezvous
or MQ Series.
As you want performance, you should do the minimum work possible to
get the data on the queue then post-process the data in a separate
process, whose resources you can control. For instance, if the data
comes from 5 files, don't open and read them in the trigger, just put
a transaction ID on the trigger queue, read that queue in a separate
process which assembles that record and places that on the reporting
queue. If the data is in the record that fires your trigger and you
don't need to read other files, then put the data directly on a
reporting queue.
Your receivers are written in .Net code and monitor the queue (you
probably want a publish/subscribe queue [one writer, many readers]
with a message expiry time), pick off records as they arrive and
update whatever it is they update such as adding a datapoint to a
chart or an excel sheet and so on.
You might think that sounds complicated, but everything you need for
this is already out there in example form, especially if your server
is a Windows system. Triggers are documented for jBASE and are written
in jBC/BASIC, CALLdotNET is trivial, and MS provide tons of examples
of message queues and it comes with your Windows operating system. The
same applies to other message queue systems, and as a bank you
probably have message queues in place somewhere already and it sounds
like you already have a handle on .Net programs.
Message queues are persistent (if you need them to be), secure and
encrypted (if you need them to be) and very efficient. All
applications should be divided up into small units that interact via
message queues.
Jim
--~--~---------~--~----~------------~-------~--~----~
Please read the posting guidelines at:
http://groups.google.com/group/jBASE/web/Posting%20Guidelines
IMPORTANT: Type T24: at the start of the subject line for questions specific to
Globus/T24
To post, send email to [email protected]
To unsubscribe, send email to [email protected]
For more options, visit this group at http://groups.google.com/group/jBASE?hl=en
-~----------~----~----~----~------~----~------~--~---
