Mailing-List: contact user-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@ignite.apache.org
Date: Mon, 7 Dec 2015 04:46:41 -0800 (PST)
From: Denis Magda <dmagda@gridgain.com>
To: user@ignite.apache.org
Message-ID: <1449492401967-2158.post@n6.nabble.com>
In-Reply-To: <1449257207407-2142.post@n6.nabble.com>
References: <1449257207407-2142.post@n6.nabble.com>
Subject: Re: How is igfs:// URL resolved?
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi Kobe,

If I understood you task properly you want to map a path portion of an HTTP
request to an IGFS path.

If this is your case then I would suggest doing the following:
- create a Web application that is running in a Tomcat container;
- the application will use Ignite in the embedded mode (start an Ignite node
from the app code);
- process incoming HTTP requests as usual extracting the path part from a
request;
- take instance of Igfs from previously started Ignite node and pass the
path and content to it. Refer to IgfsExample that is a part of Ignite
bundle/sources for more details.

Regards,
Denis 


--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/How-is-igfs-URL-resolved-tp2142p2158.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.