[Mapbender_dev] Re: [SoC] Update on REST API Project [Weekly Report]

Vikas Banjara vikashbanjara at gmail.com
Tue Jul 6 12:30:03 EDT 2010


Hi Arnulf,

On Tue, Jul 6, 2010 at 1:36 PM, Christoph Baudson (Wheregroup) <
christoph.baudson at wheregroup.com> wrote:

> Hi Vikas,
>
> we also definitely need to see your code before midterm evaluations. Please
> commit so we can review and help. You already have created a branch, but
> apart from an ini file there is nothing regarding the SoC project.
>

I will ensure that my code is reviewed by the Mapbender dev team before the
mid term evaluation is over. I will commit all the code I have written
before midterm is committed to the branch.

>
> Thank you,
>
> Christoph
>
>
>
> Arnulf Christl wrote:
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Hi Vikas,
>> thanks for your report.
>>
>> There is the mid-term evaluation coming up. This means that we will have
>> to write a report. We can coordinate as we go along.
>>
>> Last weekend at the code sprint we spent some time discussing the
>> resource design required by the services and the applications objects.
>> We decided that it will be easier to first design and then implement the
>> resources and representations for applications. Karim has done some
>> preliminary work a while ago, maybe you can use some of what he has done
>> to start with.
>>
>
Can you please point me to Karim's work done in this regard.

>
>> We are still wondering how to best design and then implement the
>> resources  for services. This will be the trickiest bit as we have to
>> decide whether there will be one type of resource for all kinds of
>> services or one each. Especially when we start to include more of
>> OpenLayers as a viewer component we might also want to deal with
>> proprietary services from GoogleBingYahoo et al. There is nothing there
>> yet to build from so we will need to spend some time thinking and
>> talking. So for the time being we stay focused on what we know, that
>> includes WMS and WFS, where WFS by comparison is way more complex but
>> also way more interesting. Lets see how far we will get.
>>
>
As we have completed one use case (code review is still left, I am fine
tuning and will commit it well before the deadline of mid term evaluation),
should we now start with a new use case. So the next use case could be the
resource, WMS. Can we have a separate thread discussing this use case.


>
>> As yet we do not have a development server which is rather unfortunate
>> at this momemt. The old one at telascience seems to have crapped out
>> altogether and there is not new one at the new OSGeo service provider.
>> We are working on this. In the worst case we will have to find something
>> outside of OSGeo for the time being.
>>
>

Its ok but it would have been great to test my code better, if I could have
got an account on any server. Anyways, I will not make this unavailability
of server any hindrance to the progress of the report.


Thanks
Vikas

>
>> Thanks for the good work so far.
>>
>> Best regards,
>> Arnulf.
>>
>> Vikas Banjara wrote:
>>
>>
>>> Hi all,
>>>
>>> This week, I complete the User use case. I can now get, post and put on
>>> the
>>> resource USER. I have used this article as reference while implementing
>>> this
>>> resource: http://www.mapbender.org/Resource:User
>>>
>>> There are issues with the implementation. Currently I expose all the
>>> columns
>>> of a table. I need to fine tune this so that I expose only required
>>> columns
>>> of the table. For example when there is a get request on a user id , the
>>> api
>>> returns the entire row of the user id which includes the password also.
>>> This
>>> should be a big NO. I will fine tune this in coming week. I will discuss
>>> this with the mentor Seven and other mapbender devs.
>>>
>>> In the next week, I will start discussing a new use case and will then
>>> start
>>> working on the same. In the mean time I will also fine tune User
>>> resource.
>>>
>>> Thanks
>>> Vikas
>>>
>>>
>>>
>>> ------------------------------------------------------------------------
>>>
>>> _______________________________________________
>>> SoC mailing list
>>> SoC at lists.osgeo.org
>>> http://lists.osgeo.org/mailman/listinfo/soc
>>>
>>>
>>
>>
>> - --
>> Nothing makes sense, except we make it.
>> http://www.metaspatial.net
>>
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.4.9 (GNU/Linux)
>> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>>
>> iEYEARECAAYFAkwy24kACgkQXmFKW+BJ1b2HZACeN5LZ8dxU1oYyXNZ+0RCSOtaH
>> IgMAn1+PxAiIQ4rRfKEJUGdCuM/OiJ7q
>> =FC9P
>> -----END PGP SIGNATURE-----
>> _______________________________________________
>> Mapbender_dev mailing list
>> Mapbender_dev at lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/mapbender_dev
>>
>>
>
>
> --
>
> ********************************************
> AGIT 2010
> 7.-9. Juli 2010 in Salzburg
> Treffen Sie die WhereGroup an Stand Nr. 30
> http://www.agit.at
> ********************************************
> ----------------------------------
>
> Aufwind durch Wissen!
>
> Qualifizierte OpenSource-Schulungen
> bei der www.foss-academy.eu
>
> ----------------------------------
> _______________________________________
>
> W h e r e G r o u p GmbH & Co. KG
>
> Siemensstraße 8
> 53121 Bonn
> Germany
>
> Christoph Baudson
> Anwendungsentwickler
>
> Fon: +49 (0)228 / 90 90 38 - 15
> Fax: +49 (0)228 / 90 90 38 - 11
> christoph.baudson at wheregroup.com
> www.wheregroup.com
> Amtsgericht Bonn, HRA 6788
> _______________________________________
>
> Komplementärin:
> WhereGroup Verwaltungs GmbH
> vertreten durch:
> Olaf Knopp, Peter Stamm
> _______________________________________
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/mapbender_dev/attachments/20100706/060d3a21/attachment.html


More information about the Mapbender_dev mailing list