users@grizzly.java.net

Re: WELCOME to users_at_grizzly.dev.java.net

From: Survivant <survivant00_at_gmail.com>
Date: Tue, 4 Mar 2008 17:30:23 -0500

they are not proxies.

Basicaly, they received trades and parse them and save them into a dabatase.
Some of them could send a formated message to MQSeries.

The others applications are not currently corrected to the gateways.
They(the clients) feed directly from the database.


If I choose one of the gateways that I want to migrate, it a gateway that
have 2-3 connections to extern providers like (YSX, Nasdaq..) and receive
multiple requests from the clients.

Like a client will connect to the server, ask for a stock's quote and
disconnect when the quote is received. One other client will get a
permanent connection to the gateway and act like a feed. This client will
subscribe to a particuliar stock, and each update done to this stock will be
send back to the client.

that's the kind of application that we have.

----- Original Message -----
From: "Oleksiy Stashok" <Oleksiy.Stashok_at_Sun.COM>
To: <users_at_grizzly.dev.java.net>
Sent: Tuesday, March 04, 2008 11:34 AM
Subject: Re: WELCOME to users_at_grizzly.dev.java.net


Hi Sebastien,

> How do I create a Basic server (like your echoserver) that will accept
> multiples connections made from non NIO clients (like telnet) ?
It doesn't matter. Server can work with TCP or UDP clients regardless
the way they implemented.

>
> I will like to have the blocking and non blocking option (for our legacy
> gateways, they wait until a timeout).
Grizzly works currently in non-blocking mode in other words uses NIO,
which provides better performance for bigger amount of clients and
better scalability.
>
> The gateways are connected to the markets (TXS, Bloomberg..) and the
> volumes of trades received is pretty high. My objective is to create a
> template gateway that will received incomming connections and just
> replace the default connector by one different depending of the market
> feed.
It means gateway will work as load balancer and redirect requests to
different points depending on there loading? In other words gateway
will work as proxy between client and target market points?
Are you planning to parse incoming messages on server side or you just
need to redirect them?
I just want to understand better how gateway should process requests.

In any case, think, it should be enough easy to build some proxy like
server.

Thanks.

WBR,
Alexey.

>
>
> Anyone can help me to start ?
>
> merci Sébastien
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
For additional commands, e-mail: users-help_at_grizzly.dev.java.net