Re: New adopter questions

This will depend on the availability of CIM-RS protocol in
public(personally I dont know, will check soon the status), We would
certainly be interested to take this further.
I will be pushing the topic in our next architecture call, You may join the
call, I will update the the details of call which is on Thursday and We
will discuss,



On Fri, Mar 1, 2013 at 9:54 PM, Anuj Jain <[email protected]> wrote:

> Thank you Devchandra!
>
> That clears up quite a bit.
>
> I look at the combination of CIM-RS and a simple webserver in Pegasus as a
> huge advantage.
> With traditional, heavy UIs (Java Applet/Application), a CIMClient was
> fine with no need for a webserver. But with modern implementation of the
> UIs with HTML5/Ajax, REST & JSON seems to be the path ahead. Today, such an
> implementation needs Pegasus for your object model and then an external
> (external to Pegasus) webserver to pull information from the CIMOM and
> translate it into JSON for your UI. This external webserver additionally
> serves up html/css/js and mime content.
> This combination of CIM-RS (or its likes) with Pegasus's ability to be a
> simple webserver serving html/css/js pages along with some mime content
> would eliminate the need of an external webserver.
> Consider this my request for the webserver feature :-)
> The obvious next question is, how can we drive this initiative further?
>
> Thanks again!
> Anuj
>
>
> On Fri, Mar 1, 2013 at 10:51 AM, Devchandra L Meetei <[email protected]>wrote:
>
>> This view is soley my understanding and does not represent the view of
>> pegasus community.
>> Yes, PEP #362 was not implemented as the DSP was not public yet, It was
>> work in progress. Once it becomes public, I am inclined to believe that it
>> will be implemented, Many users are interested.
>>
>> Aah, Regarding the webadmin interface again, Should it a part of 2.13?
>> Community is discussing, We have
>> http://bugzilla.openpegasus.org/show_bug.cgi?id=9219 which has most of
>> the implementation, But we may require some tweaking.
>> Should a user request it, community will certainly try hard to push in
>> 2.13.
>> --
>> Warm Regards
>> --Dev
>> OpenPegasus Developer
>> "It's Always better to try and fail instead of not doing/trying anything"
>>
>>
>>
>>
>> On Fri, Mar 1, 2013 at 8:40 PM, Anuj Jain <[email protected]>wrote:
>>
>>> Hi,
>>> I am not so new to Pegasus but its been a while since I have been
>>> involved with it. Last I was involved with Pegasus was 2008 and the
>>> community and the product have come a long way!
>>>
>>> I am researching Pegasus's features for adopting it as a CIMOM. I have a
>>> couple of questions.
>>>
>>> - CIM-RS (JSON) support: After browsing through a lot of documentation
>>> on the Open Pegasus site, I see mentions of CIM-RS implementation. The
>>> ManDevCon presentation has some reference to it. I also found PEP # 362.
>>> But I do not see any traces of the implementation. Is this implemented
>>> (even if partially) in a separate branch?
>>>
>>> - Web Admin to the CIMOM: Again, looking through the site, I came across
>>> mentions of something that to me seemed like a web interface to the CIMOM
>>> (only for CIMOM admin). Is there something like this present in Pegasus? If
>>> so, can someone please point me to some documentation/help of enabling this
>>> feature.
>>>
>>> Your help is greatly appreciated.
>>> Thank you
>>> Anuj
>>>
>>
>>
>>
>>
>>
>


-- 
Warm Regards
--Dev
OpenPegasus Developer
"It's Always better to try and fail instead of not doing/trying anything"