[Sugar-devel] Help required with webservices
prasoon92.iitr at gmail.com
Mon Jun 9 15:27:34 EDT 2014
On Mon, Jun 9, 2014 at 2:56 AM, Sam Parkinson <sam.parkinson3 at gmail.com>
> On Jun 9, 2014 5:49 AM, "Prasoon Shukla" <prasoon92.iitr at gmail.com> wrote:
> > Now, the question. I've been told a few times to use the existing
> webservices mechanism to store a user's session so that the user won't need
> to login every time he opens the activity. However, there is no need for
> it, IMO. The activity, as I've mentioned already, is a web browser, of all
> things, and can happily store cookies so that users will be logged in every
> time they open the activity.
> I think people wanted a way to sign in automatically with out
I asked Paul something along these lines. Here's his reply (and I concur):
When you're dealing with schools and classroom environments you're probably
going to some measure of laptops getting swapped around. For instance, at
the end of the year will each child take their XO into their next classroom
- or will the XO stay at the classroom and the kids use different XOs each
year? It's up to the school to decide how they handle it, and they might do
it differently. Alternatively, there might be a school with 250 students
and 50 XOs (two classrooms) - and classrooms share the XOs, class A gets
them for a month, and then class B gets them next month.
So, how do we distinguish two different people using the same XO? A user, I
suspect, will want to track his account personally. Also, the user history
serves a role in establishing the user's credibility in the community. So,
we can't tie up the identity of a user to a XO. And therefore, I don't
think that think approach will work, IMHO.
> So browse activity (or social help activity) can generate a:
> * unique user id
> * avatar from the users XO colors
> * name (from sugar username)
> * and maybe fake email to collect all the users notification and display
> them in sugar
> And tell this to the form software so it can automatically give them an
> account and sign them in.
Again, the problem with the identity persists.
> I also want to try and do something like this for the ASLO, so maybe we
> can work together?
Well, I don't really know much about the ASLO, except that it's the
sugarlabs server. Nevertheless, I don't see a problem with integrating this
- discourse (with some dependencies) needs to be installed on the server
side and that's pretty much it :)
> > So, what's the use of using the webservice mechanism in such a case?
> If you want have a service in the journal to put files in the cloud. Or
> of you want to view files in the cloud :)
Anyway, I'll put this on hold for the time and continue with the UI. If we
need to couple the Discourse forum with some other activity, it would then
be nice to build a webservice.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Sugar-devel