[Architecture] Jaggery Language Review14/03/2012 - [Minutes]

Samisa Abeysinghe samisa at wso2.com
Thu Mar 15 20:17:16 PDT 2012


Please clearly mark what is 1.0.0 vs what is post 1.0.0.

On Fri, Mar 16, 2012 at 5:42 AM, Sanjiva Weerawarana <sanjiva at wso2.com>wrote:

> On Thu, Mar 15, 2012 at 11:06 AM, Nuwan Bandara <nuwan at wso2.com> wrote:
>
>> log()
>>
>>    - Need to change the current log function to be a class with multiple
>>    options such as,
>>       - A way to handle log levels (isDebugEnabled etc)
>>    - So a simple sample would look like
>>
>> var log = new Log()
>>
>> log.error(message)
>>
>>
> Also the note Azeez sent please ref named loggers. Also need a way to
> control log level from both inside the app and outside the app.  Please
> review that design here too ...
>
> Feed
>>
>>    - At present we have multiple Feed objects, we will be merging all
>>    these together and have one Feed object to handle Atom and RSS feed reading
>>    and writing.
>>
>> var feed = new Feed(url) or var feed = new Feed(xmlObject)
>>
>>  feed.title
>>
>>
> Please make sure the Feed(url) guy somehow ties into the HTTP Client stuff
> .. otherwise you'll have to sort out different ways to give creds etc. when
> the URL access becomes non-trivial.
>
> You'll also need to be able to write out a feed nicely. JSONify on a Feed
> object should of course give a JSON representation of the object but to
> write it out as an Atom feed, we can have two choices:
>
> print (feed.toString()) or print (feed.toXML()) or print (feed.toAtom())
>
> OR
>
> write (response) or writeAtom (response) / writeRSS1 (response) /
> writeRSS2 (response)
>
> Which is more natural from a JS perspective? Who is responsible for
> setting the media type etc.? If we do the latter form we can make the Feed
> object write out the whole thing including media type and also write it out
> without stringifying the whole thing.
>
> File
>>
>>    - File need to take path relatively to the current location.
>>
>> Lose readLine()?
>
>>
>>
>> Database
>>
>>    - Need to cleanup the API and remove savepoint functions since its
>>    hardly used
>>    - Need to put up a complete sample with all the usecases
>>
>> Registry
>>
>>    - Need to rename as *MetaDataStore*
>>    - There will be one registry location and user is not aware of it. we
>>    will be allocating a place in governance registry
>>    - a sample will look like
>>
>> var metaStore = new MetaDataStore()
>> var res = metaStore.newResource()
>> res.addProperty('url', 'http://wso2.com')
>>
>> metaStore.put('myProp', res);
>>
>>
> Bad example; metaStore.put ('/a/b/foo', res) :-).
>
> I am still not satisfied with only having a relational storage story. Yes
> CouchDB is easy to add on but we can't include it in the simple integrated
> runtime because of Erlang.
>
> We did some work in the early days on striping JSON into Cassandra. Does
> anyone know what the status of that work is? Gokul did it IIRC .. can we
> resurrect/finish that?
>
> Sanjiva.
> --
> Sanjiva Weerawarana, Ph.D.
> Founder, Chairman & CEO; WSO2, Inc.;  http://wso2.com/
> email: sanjiva at wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1
> 650 265 8311
> blog: http://sanjiva.weerawarana.org/
>
> Lean . Enterprise . Middleware
>
> _______________________________________________
> Architecture mailing list
> Architecture at wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
> Thanks,
Samisa...

Samisa Abeysinghe
VP Engineering
WSO2 Inc.
http://wso2.com
http://wso2.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.wso2.org/pipermail/architecture/attachments/20120316/7858713d/attachment-0001.html>


More information about the Architecture mailing list