Managing Jcloud Context

["Zitony, Eyal" <ey...@hp.com>]

Hi All,

I'm using Jcloud in order to access HP Helion object store.
I have a Java application running on a tomcat server.
In order to work efficiently with the Jcloud, I'm thinking if it will make sense to hold an instance of a BlobStore or a BlobStoreContext as a Bean member? The motivation is to reduce the need to perform the initialization and the authentication upon each call.

Do you guys think that this is a correct approach? I have some concerns, for example, will the Jcloud context be aware if the authentication token has been revoked and re authentication is required?

Thanks

Eyal

RE: Managing Jcloud Context

["Zitony, Eyal" <ey...@hp.com>]

Thanks!
That’s the answer I was hoping to get…

Eyal

From: Adrian Cole [mailto:adrian.f.cole@gmail.com]
Sent: יום ד 19 נובמבר 2014 17:32
To: user@jclouds.apache.org
Subject: Re: Managing Jcloud Context


Hi, Eyal!

I will give you a short answer.

In current design, jclouds contexts are relatively expensive to create. They are designed to be shared, and outlive sessions. If you have a problem with token renewal, that would be a bug.

Hope this helps!
-A
On Nov 19, 2014 5:05 AM, "Zitony, Eyal" <ey...@hp.com>> wrote:
Hi All,

I’m using Jcloud in order to access HP Helion object store.
I have a Java application running on a tomcat server.
In order to work efficiently with the Jcloud, I’m thinking if it will make sense to hold an instance of a BlobStore or a BlobStoreContext as a Bean member? The motivation is to reduce the need to perform the initialization and the authentication upon each call.

Do you guys think that this is a correct approach? I have some concerns, for example, will the Jcloud context be aware if the authentication token has been revoked and re authentication is required?

Thanks

Eyal

Re: Managing Jcloud Context

[Adrian Cole <ad...@gmail.com>]

Hi, Eyal!

I will give you a short answer.

In current design, jclouds contexts are relatively expensive to create.
They are designed to be shared, and outlive sessions. If you have a problem
with token renewal, that would be a bug.

Hope this helps!
-A
On Nov 19, 2014 5:05 AM, "Zitony, Eyal" <ey...@hp.com> wrote:

>  Hi All,
>
>
>
> I’m using Jcloud in order to access HP Helion object store.
>
> I have a Java application running on a tomcat server.
>
> In order to work efficiently with the Jcloud, I’m thinking if it will make
> sense to hold an instance of a BlobStore or a BlobStoreContext as a Bean
> member? The motivation is to reduce the need to perform the initialization
> and the authentication upon each call.
>
>
>
> Do you guys think that this is a correct approach? I have some concerns,
> for example, will the Jcloud context be aware if the authentication token
> has been revoked and re authentication is required?
>
>
>
> Thanks
>
>
>
> Eyal
>
>
>
>
>